What "you own the code" should mean in a web contract
Suppliers say it, contracts rarely define it. The five things ownership must include, the phrases that quietly take it away, and how to check before you sign.
The short answer
“You own the code” is one of the most repeated promises in web proposals and one of the least defined in web contracts. Real ownership is not a sentence. It is five practical things, and if any of them is missing, you own a promise rather than a website.
The five things ownership must include
- The source, not just the output. The code as the developers wrote it, including build configuration, dependency lists and deployment setup. A folder of finished pages is a snapshot, not a codebase.
- In a repository you control. A repository under your organisation’s account, with the supplier as a collaborator. Not the other way around. If the supplier can remove your access, you do not control it.
- The right to change it. By anyone you choose, without permission. Clauses that restrict modifications, or require the supplier for changes, are licences in disguise.
- The right to host it anywhere. The site must build and run on a standard platform without secret ingredients. Ask what happens if you move it to another host tomorrow.
- Nothing revocable. For any shared components the supplier reuses across clients, a perpetual, irrevocable licence to keep using them in your project. Fair to both sides, and it cannot be withdrawn in a dispute.
Phrases that quietly take ownership away
| Phrase in the contract | What it usually means |
|---|---|
| ”Licence to use the website” | You may use it, they own it |
| ”Ownership transfers on full payment” | Fine, as long as full payment is defined and reachable; check the milestones |
| ”Excluding proprietary components” | Ask which ones; if the answer is “the framework”, the site does not work without them |
| ”Hosted on our platform” | Often means the site cannot run elsewhere without a rebuild |
| ”Access to the repository during the engagement” | Access ends when the engagement ends |
| ”Deliverables: the live website” | The output, not the source |
The practical test
Forget the legal language for a moment and ask one question: if your supplier stopped answering tomorrow, could another competent developer take over within a week, without needing anything from the old one?
That requires the repository, the build instructions, the hosting and domain accounts in your name, the secrets and API keys stored somewhere you can reach, and documentation that explains how the pieces fit. If any of those lives only with the supplier, that is the gap to close, ideally before launch.
Why we build this way on purpose
Ownership is easier to deliver with some approaches than others. Code in a standard framework, in a repository under your account, deployed to a platform in your name, is owned by you in every sense above. A page-builder site or a licensed theme cannot be owned that way no matter what the contract says, because the platform holds the layout. That is not the only reason we build in code, but it is a large one.
What this means for you
Before you sign, ask for the ownership clause and check it against the five things. Ask to see how a previous client’s repository is set up. Ask how a handover works. Three questions, ten minutes, and you will know whether “you own the code” is a fact or a slogan.
Frequently asked questions
Is "you own the code" standard?
It is commonly promised and inconsistently delivered. Contracts often grant a licence to use the site rather than transferring the code, or transfer the code but exclude the tooling needed to build and deploy it. Ask for the exact clause and read it as if the relationship had already ended.
What about the parts the supplier reuses across clients?
Reusable components and libraries are normal and fair. The contract should grant you a perpetual, irrevocable licence to keep using them in your project, so the supplier keeps their toolkit and you keep a working site. What must not happen is a clause that lets them withdraw that licence.
Do I own a page-builder or theme-based site?
Rarely in any useful sense. You own your content and images. The layout lives in the builder's platform, and a theme's licence usually stays with the supplier or the theme vendor. That is one reason we build in code: ownership is a property of the approach, not just of the contract.
Can I check ownership before signing?
Yes. Ask for the ownership clause, ask to see the repository setup of a previous client project, and ask how a handover to another developer works in practice. A supplier who owns nothing of yours will answer all three easily.