Code ownership

Your code. Your call.

Everything we build for you is yours — with its full history. A copy is free, any time. And if you ever move on, the move has one fixed price, agreed in writing before anything is touched.

REPO Source code
DATA Database
FILES Uploads & media
SRVR Application server
DNS Domain & DNS
MAIL Email accounts
BKUP Backups

Ask for a copy of everything Plan a move

The register

What you own, and where it lives.

Asset	What it is	Where it lives	Copy 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.

Free, always

What we never charge for.

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 or per-file charge — the decision to leave costs nothing
Anything beyond the engineering in the move — we never charge you to receive what is already yours

If you ever leave

A move in days, not months.

Day 0

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 reason required, no conversation about staying, and no clock on your right to leave.

You: Submit the request · Us: Acknowledge within one business day
Day 1

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 price for the whole job. We work that price out from the team your project is currently running on and the notice we owe them, then put it in front of you before anything is touched. Nothing on it is a surprise, and nothing is hourly.

You: Approve the plan · Us: Asset inventory + fixed price, in writing
Day 2

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.

You: Create the account, set the password, share it · Us: Tell you exactly what to provision
Day 3–4

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: Nothing. Carry on trading. · Us: Provision, transfer, configure, harden
Day 5

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.

You: Verify and sign off · Us: Fix anything you find, at no extra cost
Cutover

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: Pick the window · Us: Switch DNS, monitor, stand by
Same day

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.

You: Change the passwords, keep the pack · Us: Confirm we hold nothing, in writing

One-time transfer fee · agreed before we begin

Quoted in writing.

Fixed, not hourly. Confirmed before a single file moves — and you can stop there, with nothing owed.

Team allocated

Which engineers are on your project today, and which of them the move genuinely needs.

Notice period

The notice we are committed to for that team while your work is documented and handed over cleanly.

Size of the move

What is actually travelling — servers, data volume, integrations, email, DNS and the destination stack.

The fee includes

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 in the fee

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)

Where it runs

Hosted in the region you choose.

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

Asia-Pacific

Mumbai, IndiaMUM
Singapore, SingaporeSGP
Sydney, AustraliaSYD

Americas

Vint Hill, Virginia, USAVIN
Hillsboro, Oregon, USAHIL
Beauharnois, Quebec, CanadaBHS

Europe

Gravelines, FranceGRA
Roubaix, FranceRBX
Strasbourg, FranceSBG
Limburg, GermanyLIM
Warsaw, PolandWAW
London, United KingdomERI

Which locations are available depends on the product and on current capacity — we confirm the exact datacentre in your plan before anything moves.

And if you ever come back

If you ever choose to begin again with us, we will be here — and we will support you in every way we can.

Leaving is not a falling-out, and it is not a door closing behind you. If the new arrangement does not work out, if your next team moves on, or if one day you simply want us back on it — write to us. We will pick your project up from wherever it stands: the same people wherever we still can, the same standards where we cannot.

Always answered

Ask us anything about a system we built and you get a straight answer — whether you are a client at that moment or not.

Nothing to re-earn

No re-joining fee, no cooling-off period, no penalty for having left. You come back as a client, not as a case.

Resumed, not restarted

Your repository, its full history and the handover pack mean we continue from where things stopped — never from zero.

Same address, however long it has been. [email protected]

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 transfer fee applies only when you ask us to run the 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 is there a fee at all, 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.

Why is the fee not published as a number?

Because a number published in advance is a guess, and a guess is either padded to be safe or corrected upwards later. Neither is how we want to end a relationship. We look at the team your project is currently running on, the notice period we are committed to for those engineers while your work is documented and handed over, and the real size of the move. That becomes one fixed figure, in writing, before anything is touched — and if it does not suit you, you stop there and owe nothing, with your code and data still yours to take.

What does the notice period have to do with my migration?

Your project is staffed by named people, not a pool. When you leave, those engineers spend their remaining committed time writing your work down properly — runbooks, environment notes, deploy steps — so that whoever takes over is not guessing. That handover time is real, and it is part of what the fee covers. It also means a clean exit rather than a sudden one, which is the point of doing it this way.

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 moving — just want it in your hands?

Ask for your code today and it’s yours today, at no cost. A client who can leave easily is a client who stays on purpose.

Ask for a copy of everything WhatsApp us

Your code. Your call.

What you own, and where it lives.

What we never charge for.

A move in days, not months.

You raise the request

We send the transfer plan

You create the new home — and the password

We move everything

You test it side by side

We point the domain

You change the password. We are locked out.