Rent, own, or subscribe? A plain-English guide to website ownership.

“Do I own my website?” sounds like a simple question. It isn't. There are actually four different things wrapped inside every website, and most businesses own some of them and rent others without realizing it.

Here's the breakdown, and why the answer matters less than you'd think.

The four things a “website” is made of

1. Your domain

You buy this on a registrar (GoDaddy, Namecheap, Cloudflare, etc.) and you own it forever as long as you keep renewing — typically $15/year. This one's easy: always register your own domain, at a neutral registrar, with your own payment method. Never let an agency or platform register it “for” you under their account.

2. Your content + data

Your copy, your images, your customer list, your lead submissions, your analytics. This should always be yours, exportable as CSV/zip whenever you ask. Good agencies make this explicit. Platforms like Shopify and Mailchimp let you export. Some older CMSes and proprietary platforms make this painful on purpose.

3. Your hosting

The actual server running the site. You can own this (your own Vercel/AWS/etc. account), or someone else can host it for you (any agency with a subscription model, or any DIY platform like Wix/Squarespace). Hosting ownership is actually less important than people think — moving hosts is a weekend project if you own the code.

4. Your code

The actual application that generates the site. This is the one where the rent/own/subscribe distinction genuinely matters.

Three common arrangements

Renting (Wix, Squarespace, default Shopify themes)

You pay a monthly fee. You don't own the code and you can't take it with you. If the platform raises prices, kills a feature, or goes under — you start over. The trade-off: cheap, fast to set up, no technical knowledge needed.

Good for: businesses under $500k/year in revenue where the website is purely informational.

Buying (custom agency build, typically $10k–$50k upfront)

You pay a large fee once and walk away with the source code in your own GitHub repo. You own the code forever. But you're also responsible for hosting it, maintaining it, updating dependencies, fixing bugs, and handling security patches. If you don't do any of that, your shiny owned website gradually rots.

Good for: larger businesses with in-house technical staff or a long-term retainer agency relationship.

Subscribing to a managed service (our approach)

Between rent and own. You pay a monthly fee that covers hosting, code, maintenance, security updates, and ongoing improvements — but unlike Wix/Squarespace, the code is real production-grade code (not a drag-and-drop constraint), and there's a clear buyout option at any time. You own your domain, content, and data; we own the code; you can buy it out ($9,500 at Orbit) whenever you want to take it and go.

Good for: small and mid-sized businesses that want the performance of a custom build without the upfront cost or the ongoing maintenance burden.

So do you actually need to own your code?

Probably not. The real questions to ask instead are:

• Can I leave? What's the exit path? Is it priced? Is it in writing?
• Can I take my data? Content, customers, leads, analytics — all exportable?
• Am I locked into their pricing? If they double the fee, what's my alternative?
• What happens if they disappear? Is there a contingency plan?

A good subscription arrangement answers all four: yes, yes, no (price locks + buyout option), and you get the code in an emergency. A bad subscription arrangement (Wix, lots of “web designer” outfits) fails most of them.

The Orbit approach

We're explicit about this in our Service Agreement: you always own your domain, content, leads, and data. We own the source code during your subscription. You can buy it out anytime for $9,500 (same price, no escalation, written in the contract). If we ever wind down, we hand you the code repo and 60 days of migration help at no charge.

That's different from Wix/Squarespace (no buyout possible) and different from a traditional $20k agency build (huge upfront, ongoing maintenance is your problem). It's the middle path — and for most small businesses, it's the one that actually makes sense.