Ownership · Custody · Exit
Your code is yours.
Here is the door —
and the key.
Everything we build belongs to your business from the first commit: the source code, the database, your files, your domain. This page shows what you own, where it is hosted, and the seven steps to move it onto servers you control — whenever you decide. No notice period. No exit penalty. No conversation about staying.
A full export of your code and data is free, any time — migrating or not. The fee below is only for us to run the move for you.
Note that the Owner column never moves. It is yours in both positions — only operations change hands.
Where it runs
Hosted on OVHcloud — and rentable in your own name.
We host client systems on OVHcloud rather than a reseller panel, for one reason that matters to you: it is an account you could hold yourself. There is no proprietary layer between your software and the machine, nothing that only works while we are involved, and nothing you would have to rebuild to leave.
You also choose the country your data sits in. We run client systems from India, the United States, Canada, Europe, Singapore and Australia — so you can keep records close to your customers, or inside the borders your regulator expects.
If you want the account in your name from day one, say so at project start. We will build inside your OVHcloud account, on your billing, with you as the account holder from the first commit — and then there is nothing to migrate later. You simply remove our access.
Infrastructure sheet
- Provider
- OVHcloud — an independent global cloud provider that builds and runs its own datacentres
- Regions
- India, USA, Canada, Europe, Singapore & Australia — you pick the one your data lives in
- Data residency
- Your data stays in the region you chose. It is not copied to another country without your say-so.
- Account holder
- Ours by default — or yours from day one, if you ask at project start
- Root access
- Handed to you on request, at any point in the relationship
- Isolation
- Your application runs in its own environment, not shared with another client
Where we can put your servers
Asia-Pacific
Americas
Europe
Which locations are available depends on the product and on current capacity — we confirm the exact datacentre in your plan before anything moves.
The register
What you own, line by line
Not a summary — the actual list. The last column is what you can have today, without starting a migration and without paying anything.
| Asset | What it is | Where it lives | How you take it today |
|---|---|---|---|
| Source code | Every line we write for you, with the complete Git history behind it. | Your Git organisation, or ours mirrored to yours | Ask, and we push it to your account the same day. Free. |
| Database | Your live business data — customers, orders, records, everything. | OVHcloud, in the region you chose | Encrypted dump on request, any time. Free. |
| Uploads & media | Files you and your users have uploaded. | OVHcloud object storage | Downloadable archive on request. Free. |
| Application server | The machine your software actually runs on. | OVHcloud | Root access on request — or we build in your own account from day one. |
| Domain & DNS | Your address on the internet. | Your registrar account, in your name | Already yours. We hold edit rights only where you asked us to. |
| Email accounts | Your mailboxes and their contents. | Your mail provider, or ours if you asked us to host it | Exported in a standard format, or synced straight to your new provider. |
| Backups | Snapshots plus the scripts that restore them. | OVHcloud, separate from the live server | Handed over with the restore runbook. |
| Documentation | Runbooks, environment variables, deploy steps, architecture notes. | Inside your repository | Ships with the code. Nothing lives only in our heads. |
Migration
Seven steps to move out
This is the whole process, in order, with who does what at each stage. Most migrations finish in three to five working days. Nothing moves — and nothing is charged — until you approve the written plan at step two.
You raise the request
Fill the form at the bottom of this page. Tell us which system is moving, where it is going, and when you want it done. No notice period. No reason required. No conversation about staying.
We send the transfer plan
A written plan: the exact list of assets moving, the order they move in, the downtime window, the rollback plan, and one fixed invoice. Nothing on it is a surprise and nothing is hourly.
You create the new home — and the password
You open the new hosting account in your own name, with your own billing card, and you set the password yourself. Then you share it with us for the transfer window only. We never create the account you are supposed to own.
We move everything
Code, database, uploaded files, cron jobs, queues, environment variables, SSL. Your live system keeps running untouched the entire time — the move happens alongside it, never on top of it.
You test it side by side
The new environment goes live on a temporary address. You open both, click through the parts that matter to your business, and sign off. Nothing switches over until you say so.
We point the domain
In the window you picked, monitored end to end. The old server stays online in read-only for 14 days afterwards, so there is always a way back.
You change the password. We are locked out.
The moment the migration is signed off, you change every password you shared. Our access ends the second you do — not when we get around to it. You keep the handover pack: credential list, runbook, architecture notes, deploy steps.
The proof
You hold the key the entire time.
Trust is easy to promise and hard to prove. So the migration is built around one fact you can verify yourself: at no point do we hold a password you cannot cancel without asking us.
01 · CREATE
You open the account
The new hosting account is opened by you, in your name, on your card, with a password only you have chosen. We never create the account you are meant to own.
02 · LEND
You lend it, for the window
You share that password for the transfer window only. Everything we do with it is listed in the plan you already approved — nothing else.
03 · REVOKE
You change it. We are out.
On sign-off day you change the password. Our access ends the second you do — not when we get round to it. We confirm in writing that we hold nothing.
The price
One price, written down.
US$1,000
One-time transfer fee
Fixed, not hourly. Quoted before anything moves. It covers the engineering work in the move itself — never the handover of what is already yours.
Start a migration requestIncluded
- Written transfer plan and full asset inventory
- Complete copy of code, database, files and configuration
- Provisioning and configuration on your new server
- SSL, DNS and email cutover
- Side-by-side verification, and fixes for anything you find
- The old server kept online for 14 days as a rollback
- Handover pack: credentials, runbook, architecture notes
- 30 days of email support for whoever takes over
Not included
- Your new hosting bill — paid by you, to your provider, directly
- Domain or registrar fees
- New features or redesign requested during the move
- Rewriting the software for a different stack (quoted separately)
Never charged
- A copy of your source code — free, any time, migration or not
- A copy of your database and files — free, any time
- An exit penalty, notice fee, or per-file charge — there is none
Request a migration
Tell us what to move, and where.
You are not asking permission — you are booking a job. Everything below is what our transfer team needs on day one. You will have a written plan and a fixed invoice within one business day, and you can stop at that point with nothing owed.
Straight answers
The questions clients actually ask
If we stop working together, do you hold the code?
No. There is no clause anywhere in our agreements that lets us keep your software, your data, or your domain. Ask for a copy on a Monday and you have it on Monday — whether you are leaving, staying, or just want it in your own account for peace of mind.
Can I get the code right now, without migrating anything?
Yes, and it costs nothing. Email us and we push the repository to your Git account with its full history, plus a database dump and your files. The US$1,000 is only for us to run a full server migration for you — it is never a charge for handing over what is already yours.
Who owns the intellectual property?
You do. Everything we build for your project belongs to your business once the work is paid for. We keep no licence over your product and we do not resell it. If you would like that restated in writing on your letterhead, ask and we will send it.
Why US$1,000 if the code is free?
The code is free, always. The fee pays for the engineering work in the move itself: provisioning the new environment, transferring and verifying data, re-wiring SSL, DNS, email, cron jobs and integrations, running the side-by-side test, and staying on call through cutover. It is one fixed price for the whole job rather than an hourly meter.
What happens to our passwords?
You create them, you share them for the transfer window, and you change them the day we finish. That is the whole policy. We never ask for a password that you cannot revoke yourself, and we never create the account you are meant to own.
What if your team disappears tomorrow?
The handover pack exists for exactly that. Runbooks, environment variables, deploy steps and architecture notes live inside your repository, not in our heads, so any competent developer can pick it up without us. That is deliberate — a client who is trapped is a client who cannot say yes freely.
How long does a migration take?
Most take three to five working days from approved plan to cutover. A large system with heavy data, or one moving to a very different stack, takes longer — and we tell you that in the plan, before you pay anything.
Can the server be in my name from the very first day?
Yes. Say so at project start and we build inside your own OVHcloud account, on your billing, with you as the account holder from commit one. Then there is nothing to migrate later — you simply remove our access.
Not migrating — just want it in your hands?
Ask for your code today and it is yours today, at no cost. A client who can leave easily is a client who stays on purpose, and that is the only kind we want.