Most businesses find out whether they own their website on the day they try to leave. The agency is slow to reply, the domain turns out to be registered in someone else's name, or the site only exists inside a platform it can't be taken out of.
Owning your website isn't a feeling. It's a short list of things you either hold the keys to or don't.
The five things that make up your website
1. The domain. Your address on the internet. It should be registered in your name, in an account you log into, with your email on it. Whoever controls the domain controls where your website — and often your email — points.
2. The hosting. The server or platform that serves your site. The account should be yours, with the billing in your name, so the site doesn't disappear when someone else's contract ends.
3. The code. Everything that makes the site work, kept in a repository you can access and copy. If the code only lives on someone else's laptop or inside a builder, you have a website you can use but not keep.
4. The design files. The actual source files, not screenshots or a PDF. You'll need them the next time you refresh the brand, brief a designer or add a page.
5. The accounts around it. Analytics, search console, the CMS login, form and email services. Each should be registered to you, with other people added as users — not the other way round.
Where ownership quietly goes missing
Nobody sets out to take your website. It goes missing through convenience.
- The domain was registered for you. It was quicker for the agency to buy it on their account. Years later, it's still there.
- The site lives on the agency's hosting. One monthly invoice for "hosting and maintenance" is simple, right up until you want to move.
- It's built on a platform you rent. On a hosted builder, the site only exists inside that platform. You can leave; the website can't come with you.
- The contract says licence, not transfer. Some agreements keep the rights to the code and let you use it. Read the ownership clause before the price.
- A custom CMS only they can run. If nobody else can maintain it, you're locked in by knowledge instead of by contract.
Questions to ask before you sign
Ask any studio, agency or freelancer these, and get the answers in writing:
- Will the domain and hosting be registered in my name?
- Who owns the code and the design files when the project ends?
- Where does the code live, and will I have access to it?
- If we stop working together, what exactly do I get?
- Are there fees that continue after launch, and what are they for?
A good answer to all five is short. A long answer is a warning.
How we hand a website over
At Weekone, ownership is the default, not an upgrade. On launch day we deploy to your hosting — Vercel, Netlify, Cloudflare or your own server. If you don't have hosting, we set it up with you, in your name, in about ten minutes.
The repository is transferred to you at launch, along with the design files. Code, design files, domain, hosting: nothing is rented from us.
Owning it doesn't mean maintaining it alone
Owning your site means you can take it anywhere. It doesn't mean you have to look after it yourself. Every launch includes fourteen days of fixes. After that you can keep us on a care plan — hosting management, updates and two hours of changes every month — or walk away with everything. Both are fine. That's the point.
If you'd like a website you own from day one, start your week. Still weighing up a builder? Read custom website vs website builder first.