Most people assume that paying for a website means owning it. Sometimes that’s true. Often it’s partly true in a way nobody explains until it matters.
The confusion is that “ownership” isn’t a single thing. It’s four separate things that can be held by different people, and you can genuinely own some while owning none of the others.
The four pieces
The domain. Your address on the internet. Registered to a person or company, renewed annually.
The content. Your words, your photos, your prices, your service descriptions.
The site itself. The actual files that make the pages work — the design, the code, the structure.
The hosting. The server the site lives on and the account it lives under.
You can own your domain and not be able to move your site. You can own your content but have no practical way to extract it. These are different questions and they deserve separate answers.
The domain trap
This is the most common and most damaging one, and it’s usually not malicious — just convenient at the time.
A designer registers the domain for you during setup, using their own account, because it’s faster than walking you through it. Years later you want to move, and the domain is legally theirs. If the relationship is good, they transfer it and it’s a non-event. If the relationship has soured, or they’ve stopped responding, or the business closed, you’re negotiating for your own business address.
The fix takes five minutes. Register the domain yourself, in your own name, with your own account at a registrar. Give your designer access if they need it. Access is easy to grant and easy to revoke. Ownership is not.
If a domain is already registered under someone else’s account, ask to have it transferred to yours. A reasonable answer is “sure, here’s how.” Anything else is worth paying attention to.
The exit test
Everything else clarifies if you ask one question:
If you stopped working with this person tomorrow, what would you still have?
Push for specifics:
- Would the site keep running, or does it depend on their account staying open?
- Could another developer pick it up, or would it need rebuilding from scratch?
- Could you get your content out in a usable form, or is it locked inside a platform?
- Does anything stop working if you stop paying a monthly fee?
You’re not being adversarial by asking. You’re asking what happens in the ordinary case where a business relationship ends — which most eventually do, for entirely unremarkable reasons.
Where lock-in usually comes from
Site builders. Wix, Squarespace, and similar platforms host your site on their infrastructure in their format. Your content is yours and you can copy it out, but the site itself doesn’t move — you’d rebuild elsewhere. That’s a real tradeoff, not a scam, and for many businesses it’s an acceptable one. Just know it’s the deal.
Proprietary systems. Some agencies build on their own in-house platform. This is the strongest form of lock-in, because there’s often no other developer who can take it over. Ask directly whether the site is built on something standard.
“We’ll handle the hosting.” Often genuinely convenient. The question is whether the hosting account is in your name or theirs, and whether you could move the site elsewhere if you wanted to.
Bundled monthly plans. If the build was cheap or free because it’s attached to a subscription, find out precisely what happens on cancellation. Sometimes the site goes offline the same day.
The honest tradeoff on the other side
Portability isn’t free either, and it’s worth being straight about the cost.
A site built as plain static files is maximally portable — any developer can work on it, it runs anywhere, and nothing expires. But without a content management system attached, you can’t log in and edit the text yourself. Changes go through whoever builds it, or through you editing files directly.
For a lot of small businesses that’s fine, because their site content barely changes. Services, pricing, and contact details get updated once or twice a year. If that’s you, a CMS is overhead you’d be paying for and rarely using.
But if you’re publishing regularly, running events, or updating inventory, self-editing genuinely matters, and a platform that gives you that is worth its constraints. Neither answer is correct in general. They’re correct for different businesses.
Where TruePoint sits
You register and own your domain. We’ll walk you through it if you haven’t done it before, but it goes in your name from the start.
The sites we build are static files on a standard, widely-used foundation. No proprietary platform, no in-house system only we can maintain. Any competent developer could take one over — that’s deliberate, not incidental.
Hosting runs on Netlify under your own account. Nothing depends on us continuing to exist, and nothing switches off if you stop paying us, because there’s no subscription to stop paying.
And the tradeoff applies to us too: without a CMS, you don’t edit page content yourself. If your business needs frequent self-service updates, say so early — that’s a real requirement, and it should shape what gets built rather than turning into a surprise later.
If you’re weighing this against a site builder, custom build vs. website builders goes through when each one makes sense. If you’re earlier than that and mostly want to know the numbers, what a small business website actually costs covers the ranges.