"Who owns my website?" is one of the most sensible questions a business owner can ask, and one of the most misunderstood. Most people asking it think they're asking about the code, the actual files the site is built from. They're worried they'll be handed a beautiful site they can't ever really take with them.
Here's the thing almost nobody tells you: the code was never the part that mattered. The four things that actually protect your business are your domain, your content, your customer data, and clear terms, and if you own those, you're safe, whether or not you ever hold a single line of code. Fixating on the code is like refusing to use Shopify because they won't email you their source files. Nobody wants the source files. They want their business to be safe. Let's talk about what actually keeps it safe.
The myth: "I need to own the code or I'm trapped"
This fear comes from a real place, people do get burned, but it's aimed at the wrong target. Think about the tools you already trust. You don't own Shopify's code. You don't own Squarespace's, or Wix's, or Webflow's, or the software your accountant uses. You never will, and you've never wanted to, because handing a small business owner a folder of raw code would be about as useful as handing them the engineering diagrams for their car. What would you do with it? Where would you host it? Who'd fix it?
What you actually need is for your business to keep running and to never be held hostage. That doesn't come from possessing code. It comes from owning the four things below.
The four things that actually matter
1. Your domain name
This is the big one. Your domain, your yourbusiness.com.au, is your address, your brand, and the thing every customer, Google listing and email is tied to. It must be registered in your name, under an account you control.
The classic trap isn't about code at all. It's a designer who registers your domain under their own account "to keep it simple," and then, the day you want to move on, you discover your own address belongs to someone else. That's the real hostage situation. As long as your domain is yours, you can take your brand anywhere. Lose control of it and nothing else matters. So the first question is never "do I get the code," it's "is my domain in my name and can I log in to it."
2. Your content and brand
Your words, your images, your logo, your photos, the actual substance of your site. That's yours. It's your intellectual property and it should stay that way. A fair arrangement means you can take your content and brand assets and use them wherever you like.
This matters because your content is often the most expensive part of a site to create and the easiest to carry with you. Copy that took weeks to get right, professional photography, a logo you paid for, all of it should be portable.
3. Your customer and lead data
Every enquiry, booking, and email address your site collects is your customer relationship, not the platform's. If you ever part ways with your provider, you should be able to take that data with you: your leads, your bookings, your email list, your customer records. Full stop.
This is the one people forget to ask about, and it's the one that quietly hurts most. A site that's captured two years of enquiries and a mailing list of a thousand people is holding real value. Make sure, up front, that you can get it out. A provider who'll export your data on request is treating it as yours, which it is.
4. Clear terms you understood before you signed
The final protection isn't a file, it's clarity. You should know, in plain English and before you pay, exactly what you're buying: whether it's a one-off build or an ongoing managed service, what happens if you leave, what you can take with you, and what, if anything, stays. No surprises. The problems in this industry almost never come from the managed model itself. They come from people not being told which model they were on.
Own your domain, your content and your data, and understand your terms. Do that, and the question of who holds the code becomes exactly as important as it should be: not very.
Two legitimate models (and one genuine trap)
There are two perfectly honest ways to buy a website, and they suit different owners.
The one-off build. You pay a lump sum, the site is built, and you take on hosting, maintenance, security and changes yourself, or pay someone per job. You have maximum control and, often, the code. The trade-off is that you're now responsible for keeping a live piece of software running, secure and updated, which is a real job even when nothing's going wrong.
The managed service. You pay to have the site built and then hosted, secured, updated and supported for you, usually on a monthly basis. This is the Shopify and Squarespace model, just built bespoke. You're not buying code to take elsewhere, you're paying for the site to exist and keep working without you ever touching a server. The trade-off is that the underlying build is the provider's, the same way Shopify's platform is Shopify's.
Neither is a trap. Both are how most of the web is built. The actual trap is different from either: it's a provider who holds your domain hostage, won't hand over your data, springs surprise fees, or vanishes when you need them. That's not a model, that's just a bad operator, and it can happen on either model if you don't nail down the four things above.
How we do it, plainly
Since we run a managed model, it's only fair to be straight about exactly what that means with us, because "we build and host it" should never hide a nasty surprise.
- Your domain is yours. It stays in your name and your control, and if you ever leave, we hand it over. Your address is never held hostage.
- Your data is yours. Your content, enquiries, bookings and customer list belong to you. If you leave and ask for your data, we export it and send it to you.
- We build and host it for you. You're paying us to create your site and then keep it hosted, secure, updated and supported month to month. You're not paying for a folder of code, so we don't hand the code over, the same as any managed platform. You'll always know that up front, because it's right here.
That's the whole arrangement, no asterisks. You own what makes your business yours, your brand, your address, your customers, and we take the server, security and "why is the site down at 9pm" headaches off your plate. If that sounds like the wrong fit and you'd rather own a one-off build outright, that's a completely valid choice too, and the right questions to ask any provider are in our guide to hiring a web designer without getting burned.
Your 60-second ownership checklist
Before you sign with any provider, on any model, run through these. If you can tick all five, you're protected, and it genuinely doesn't matter whether you or the provider holds the code.
- Is my domain registered in my own name, in an account I can log into? Not the designer's account "for convenience." Yours.
- Can I take my content and brand assets, my copy, images and logo, with me if I leave? They're your intellectual property; the answer should be a clear yes.
- Can I get my customer and lead data out, my enquiries, bookings and email list, on request? This is the one people forget, and it holds real value.
- Do I understand exactly which model I'm on, one-off build or managed service, and what happens if I leave? In plain English, before paying.
- Are all of the above in writing? A verbal "yeah, of course" is not a term. Get it documented.
Any decent provider will happily confirm all five, because they've built their business the honest way. If a provider gets vague or defensive on any of them, that hesitation is your answer, and it's worth more than any sales pitch.
Frequently asked questions
Who owns my website when a designer builds it?
It depends on the model. On a one-off build you typically own the finished site and often the code. On a managed service you're paying for the site to be built and hosted for you, so the underlying build belongs to the provider, like Shopify or Squarespace. In both cases you should own your domain, your content and your customer data. What matters is knowing which model you're on before you sign.
Do I need to own the code of my website?
Usually not, and most owners never actually want it. You don't own the code behind Shopify, Wix or Squarespace either. What protects your business is owning your domain, your content and your data, plus clear terms. Raw code is only useful if you have the technical setup to host and maintain it yourself.
What happens to my website if I stop paying a managed provider?
On a managed service the site is hosted for you, so if you stop the service the hosted site comes down, but you keep your domain and can take your content and customer data with you. A good provider will hand over your domain and export your data on request. Always confirm this in writing before you start.
How do I make sure I'm not locked in?
Check three things before you sign: your domain is registered in your own name and account, you can export your content and customer data whenever you want, and the terms clearly state what happens if you leave. Get those right and you're never trapped, regardless of who holds the code.
Is a monthly website service a scam?
No. Monthly managed website services are a mainstream, legitimate model, the same as Shopify or Squarespace, and they suit owners who want predictable costs and no server headaches. It only becomes a problem if a provider hides the terms, holds your domain hostage, or won't return your data. Judge the operator, not the model.
The honest bottom line
The question isn't really "who owns my website." It's "is my business safe." And your business is safe when you own your domain, your content and your customer data, and you understood your terms before you paid. Get those four things right and it genuinely doesn't matter whether you hold the code or your provider does, exactly as it doesn't matter with every other tool you already trust to run your business.
Ask any provider, including us, to spell those four out. If they answer plainly, you're in good hands. Ask us anything about ownership, or see how our builds work on our websites page.
