Who owns my website if someone builds it for me?

What exactly do you own when someone builds your site?

You own three separate things: your domain name, your content (text, images, copy), and potentially your code. Most builders will never dispute your ownership of the domain or content. The gray area is the code—the actual files and structure that make your site work.

Think of it like a house. You own the land (domain), the furniture and decorations (content), but the builder might own the blueprints and construction method (code). Which one matters most depends on your exit plan.

• Domain: Always yours if you register it independently or if the builder puts it in your name.
• Content: Your words, photos, and business information belong to you.
• Code: This is where contracts differ wildly—some builders sell it to you, others keep you locked in.
• Hosting: The server your site lives on; some builders include it, others let you choose.

Code ownership determines whether you can take your site to another builder or host it independently—and most builders don't make this easy.

Why do some builders lock you in?

Builders lock you in because it's profitable. If you can't leave without rebuilding from scratch, you're stuck paying them forever. It's not malicious—it's just business. They've invested in building your site, and they want recurring revenue.

The lock-in happens through proprietary code, custom templates, or hosting they control. You technically own the site, but you can't move it without their help (which costs extra) or rebuilding it elsewhere.

Platform lock-in is legal and common, but it costs you flexibility and negotiating power down the road.

What's the difference between owning code and owning your site?

Owning your site means you control the domain and can access your content. Owning the code means you have the actual files and can host them anywhere, on any server, with any provider. You can own your site but not the code—and that's where the trap lives.

If a builder owns the code, you're renting the site from them. You can't take it to Shopify, WordPress, or another builder without paying for a rebuild. You're locked into their pricing, their features, and their roadmap.

Owning the code is the only way to truly own your website—without it, you're leasing from the builder.

How do you protect yourself before hiring a builder?

Ask one question before you sign: 'Can I own the code and host it anywhere?' If the answer is no or vague, dig deeper. Get it in writing. A builder who's confident in their work won't hide this.

Some builders offer code ownership as a premium option or one-time purchase. Others build on platforms (like Wix or Squarespace) where code ownership isn't possible—the platform owns the infrastructure. That's fine if you're okay staying there forever.

• Ask about code ownership in writing before you start.
• Request a contract clause that specifies who owns what.
• Clarify what happens if you want to leave: can you export your site?
• Understand the hosting situation: do they host it, or can you choose?
• Know the exit costs: will moving be expensive, or is it clean?

Getting ownership terms in writing before the project starts saves you thousands in exit costs later.

What does SiteFly do differently?

SiteFly builds your site for you first—you preview it free, and you only pay if you love it. On the top tier, you can own your site's code outright and host it anywhere. You're not locked into SiteFly's platform or pricing.

This matters because it means you have a real exit option. If you ever want to move, you can. You own the code, the domain, and the content. No surprises, no lock-in fees.

SiteFly lets you own your code and host it independently—you're never trapped on their platform.

What should you do right now?

If you already have a website, check your contract or contact your builder and ask: do you own the code? Can you export it? If the answer is no, you know you're locked in. That's not a disaster, but it's good to know.

If you're building a new site, make code ownership a non-negotiable part of your decision. It costs almost nothing for a builder to give you the code, so if they won't, that's a red flag. Choose a builder who trusts you with your own work.

Asking about code ownership now prevents regret and expense later—it's the single most important contract question.