Ownership and longevity
You own the system. All of it, from the first commit.
OpsMavix builds custom operations systems and full ERP solutions that you own outright: the code, the data, the hosting account and the documentation. This page is the plain answer to the question every careful buyer asks: what happens if OpsMavix is not around.
Short version: nothing changes. The system keeps running on your own Cloudflare account, your data exports in full any day, and any competent TypeScript developer can maintain or extend it using the documentation we hand over at launch.
What is yours at handover
The code
A git repository under your organisation from day one. Every change is a commit you can read, roll back or hand to someone else.
The data
Your database, in your account. Full export in CSV or SQL from the admin screens, whenever you like, no request needed.
The hosting account
Cloudflare, in your name, on your card. You add and remove users. We are a collaborator you can revoke.
The domain and integrations
Your domain, your Shopify, Amazon, Xero and courier accounts. Connections are authorised by you and stay with you.
The documentation
A README, a runbook for the day-to-day, a data dictionary for every table and an admin guide. Written for the next developer, not for us.
The training
Recorded walkthroughs for the office and the floor, and a handover session at launch. Nobody needs us on the phone to do their job.
The stack, and why it is boring on purpose
We choose mainstream, documented technology so that the pool of people who can work on your system is large and the running cost is small. No proprietary framework, no in-house language, no black box.
| Layer | What we use | Why it matters to you |
|---|---|---|
| Language | TypeScript | The most widely used language for web systems. Easy to hire for. |
| Front end | Astro | Static-first pages that load fast on a warehouse tablet on bad wifi. |
| Back end | Cloudflare Workers | Serverless, no servers to patch, runs in 300+ locations, generous free tier. |
| Database | Cloudflare D1 (SQLite) | Standard SQL. Exportable. Point-in-time recovery for 30 days. |
| Files and cache | Cloudflare R2 and KV | Documents, labels and images in R2; fast lookups in KV. No egress fees on R2. |
| Payments and email | Your Stripe, Resend | Invoices and payments through your own Stripe account; transactional email through Resend. |
Typical running cost for a system of this kind on Cloudflare is tens of pounds a month, paid by you to Cloudflare directly. There is no OpsMavix hosting margin in between.
Exit paths, written down
- Keep running it yourself. Nothing expires. The system does not phone home and has no licence key.
- Bring in your own developer. Give them the repository and the runbook. We will do a recorded handover call with them.
- Move to another agency. Same as above. The code is standard TypeScript; the database is standard SQL.
- Move hosting. The Worker and D1 database can be re-deployed to another Cloudflare account, or the data exported to Postgres if you outgrow it.
- Migrate to a packaged ERP later. Because your data is clean and exportable, an ERP implementation starts from real records, not a spreadsheet archaeology project.
Support without dependence
- Questions are free, forever. Email or call. We answer.
- Fixes for anything we built wrong are covered by the delivery guarantee.
- Control Care (optional). Around-the-clock monitoring and a named person on call, at a fixed monthly fee you can start or stop.
- Changes and new modules are quoted as fixed-scope work, never a retainer.
- Champion training. We train one person in your team to administer users, labels, prices and settings so day-to-day changes never wait on us.
Questions finance asks
Who owns the system after launch?
You do. The code lives in a repository under your organisation, the database and hosting sit in an account you control, and the domain is yours. There is no licence to keep paying and no feature that switches off when a contract ends.
Can I export my data?
Yes, any day, in full. Every table exports to CSV or SQL from the admin screens, and the database itself is a standard SQLite-compatible store you can copy out. Nothing is held in a format only we can read.
What if OpsMavix is not around in five years?
The system keeps running. It is built on mainstream, documented technology (TypeScript, Astro, Cloudflare Workers with D1, R2 and KV) that any competent web developer can maintain. We hand over a runbook, a data dictionary and an admin guide at launch so a third party can pick it up without us.
Where is it hosted and who controls access?
In your own Cloudflare account, in your name, with your billing. You control who has access. During the build we may host a working copy on our account; it moves to yours at handover.
Do we depend on you for support?
No. Questions are free, forever. If you want someone watching the system around the clock there is an optional Control Care plan at a fixed monthly fee, and you can start or stop it at any time.
Can another developer extend it?
Yes. The stack is deliberately standard, the code is documented and the schema is plain. We are happy to hand over to an in-house developer or another agency and will do a recorded handover session as part of the project.
What about security and backups?
Cloudflare D1 keeps point-in-time backups for 30 days and the code is versioned in git. Access is by named accounts with role-based permissions inside the system. You decide who is an owner, who is office and who is floor.
See it on your own numbers
The pricing and total cost page compares an owned build against a subscription platform over five years, with your seat count and your prices.