"You'll own everything" is one of the easiest promises to make and one of the most commonly broken, usually not through malice but through vagueness. A year later you want to change providers, and you discover that "owning it" didn't include the domain, or the accounts, or a copy you can actually hand to someone else. Ownership is only real if you can walk away with everything and keep running. Here is what that requires, and the questions that confirm it before you sign.
Owning the code is only part of it
A website or app is more than its code. It's the domain name, the hosting account, the database, the images and content, the third-party services wired into it, and the credentials to all of the above. You can be handed every line of code and still be stuck, if the domain is registered under the developer's account and the site lives on their server.
Real ownership means you could, tomorrow, move the whole thing to a new provider without asking anyone's permission. Everything below is in service of that test.
The five things that must be in your name
Before any work starts, confirm these belong to you or your company, not the developer.
- Your domain name, registered in an account you control. This is the one people forget, and the most damaging to lose. Your domain is your address; whoever holds the account holds the keys.
- Your hosting and server accounts, or at minimum full admin access, so the site doesn't vanish if you part ways.
- The code repository, with your own copy and access, not a private repo you can never see.
- Every third-party account used by the site: analytics, email, payment, maps. These should be under your email, with the developer added as a user, not the reverse.
- Your content and data, exportable in a standard format, so your customer list or product catalog is never trapped inside someone else's system.
If any of these sits under the provider's personal account, you don't fully own your business's presence, whatever the contract says.
The walk-away test: if you and your developer parted ways tomorrow, could you keep the site running and hand it to someone new by end of week? If not, ask what's missing.
The questions to ask before you sign
You don't need to be technical to protect yourself. Ask these plainly, and write the answers into the agreement.
- Will the domain and all accounts be registered in my name from the start?
- When the project ends, what exactly do I receive, and in what format?
- Is the code standard and documented, so another developer could pick it up, or is it locked to your custom platform?
- Are there ongoing fees, and which of them am I free to take elsewhere?
- If I leave, will you transfer everything and remove your own access?
A straight answer to each is a good sign. Hesitation, or a lot of "don't worry about that," is worth worrying about.
The proprietary-platform trap
Some providers build your site on their own private platform. It can look like a bargain, and the work may be fine, but you can only ever edit or host it through them. The moment you want to leave, you find there's nothing portable to take. You'd be starting over.
This isn't always wrong; a managed platform can suit a business that never wants to touch the technical side. Just go in knowing the trade. Ask directly: "If I stop paying you, what do I keep?" If the honest answer is "nothing you can use elsewhere," price that lock-in into your decision.
The short version
Owning your software means owning the whole thing: code, domain, hosting, accounts, content, and the access to all of it, in your name, exportable, and transferable. Before you sign anyone, apply the walk-away test and get the five essentials in writing. A good developer will happily agree, because they plan to keep you by doing good work, not by holding your domain hostage.