What kind of product it is
A place your software runs, is built, and is kept on record.
Most business software is assembled from separate products that someone has to wire together and keep in step. Dymico is one product doing three jobs.
A runtime
Your application runs on Dymico: people use it in the browser and on their phones, and its data lives there, secured and backed up.
A workshop
i3 developers build and change your application inside Dymico. A change is tried on its own branch, then goes live when it is approved, with no release window.
A record
Every change to the code and to your data is versioned and audited: who did what, and when. Any earlier version is one step away.
Why one system
What you would otherwise buy, run and connect separately.
Each line below is usually its own product, contract and point of failure. In Dymico they share one set of users, one security model and one history.
| You need | Usually | In Dymico |
|---|---|---|
| An application | An app server, a framework and a deployment pipeline | Built in, live when approved |
| Data | A database, plus backups and encryption set up separately | Built in, encrypted per record |
| Search and reports | A search cluster and a BI tool fed by exports | Built in, on the live data |
| Background work | A job queue, a scheduler, an email and SMS service | Built in, retries by itself |
| Mobile apps | A second codebase and build process per platform | Same application, web, iOS and Android |
| Proof for auditors | Logs gathered from each system after the fact | Every change recorded as it happens |
| Altogether | Several vendors to wire together | One platform, looked after by i3 |
What's inside
Four things the platform takes care of, so your application doesn't have to.
These come with every application on Dymico. None of them is an add-on.
Building and changing
Getting from a business need to working software quickly, without risky releases.
- Live when approved
- A saved, approved change runs straight away. No build step, no downtime.
- Branches for trying things
- Changes are tested apart from the live app while people keep working.
- Proven building blocks
- Sign-in, users, email, files and payments are reused, not rebuilt for each client.
Security and control
Protection built into every record from the first day.
- Encrypted records
- Data is encrypted at rest with a key per record, and the master key stays under your control.
- Access down to the record
- Roles decide who can see and change what, all the way down to single records.
- Sign-in your way
- Password, PIN, single sign-on with your company accounts, and session rules you set.
Running reliably
The unglamorous work that keeps software up at two in the morning.
- Many clients, kept apart
- Each client's data and application is isolated from every other's.
- Background work that finishes
- Scheduled jobs and sync tasks survive restarts and retry by themselves.
- Room to grow
- Capacity is added alongside, without redesigning the application.
Knowing what is happening
Answers from the data you already hold, without exporting it.
- Search across everything
- Full-text search over your records, with no separate search system to run.
- Reports on live data
- Counts, totals and trends straight from the application.
- Connected to what you use
- Accounting, CRM, payment and identity systems connect over secure APIs.
How a change happens
You decide what changes. Nothing goes live without your approval.
The same four steps for a new application or a small rule change.
- Say what you need
Describe the outcome in business terms. We turn it into a short, clear brief.
You and i3 - We build on what exists
i3 assembles it from the platform's building blocks and your existing application.
i3 developers - You try it and approve it
You see the change on its own branch before anyone else does.
You - It goes live, and stays on record
No release window. If you change your mind, the previous version is one step away.
The platform
AI on the platform
AI helps with the work. People make the decisions.
Our developers use AI assistants to research, draft and check changes. That makes us faster, but it never takes the decision away from a person.
- A named person owns every change. Whatever an assistant drafted, someone reads it, saves it and is recorded against it.
- You see what changed before you approve. The change, the reason and the checks it passed.
- Every change can be undone. Versions are kept, so going back is a normal step.
How you get it
You don't buy a licence and work it out yourself.
Dymico comes with the people who build on it. i3 designs your application, builds it on Dymico, runs it and looks after it for as long as you want us to.
- Not a no-code tool. i3 developers write and own the code, so you get software built properly without learning a builder.
- Not just hosting. We build what we run, and we stay responsible for it.
- Not a rip-and-replace. Dymico connects to the systems you already use. Start where the value is.
Questions
What people ask before a first conversation.
Do we have to replace our existing systems?
No. Dymico connects to the systems you already run, such as accounting, CRM, payments and identity, over secure APIs. Most clients start with one process and grow from there.
Where does our data live, and who can see it?
Your data is encrypted at rest, kept apart from other clients' data, and visible only to the roles you agree. The master key can stay under your control.
What does the audit trail actually record?
Every change to records and to the application itself: what changed, who changed it and when. Sign-ins, failed logins and permission changes are recorded too.
Will it cope as we grow?
Yes. Capacity is added alongside the existing setup, so growth does not mean rebuilding the application.
How quickly can we start?
Because the building blocks already exist, a first working version usually takes weeks, not months. We agree the scope with you in the first conversation.
What if we want to leave?
Your data and your application's code are versioned and exportable, and backups can be restored with your key. We would rather keep you by being useful than by locking you in.
30-minute walkthrough
See Dymico with your own problem in mind.
Tell us what you want to build or fix. In half an hour we will show you the platform and how we would approach it.
No slides, no sales script.