Most business owners assume that paying for a website means owning it. Often that is not guaranteed. Depending on the contract and the platform, you may be renting your site, or the developer may still hold the rights to the code and design. Finding that out during a dispute or a move is expensive. Here is what to check before you sign.

This article is general information, not legal advice. Have a lawyer review any contract before you sign.

The four things that make up “your website”

  1. Source code: the files that make your site work.
  2. Design and content assets: layouts, logos, images, fonts, and copy.
  3. Domain name: your web address, such as yourbusiness.com.
  4. Hosting and accounts: the servers and services your site runs on.

You should have clear rights to all four. Losing any one can leave you stuck.

What is vendor lock-in?

Vendor lock-in happens when your site depends on a provider’s proprietary platform, hosting, or accounts so that leaving means rebuilding from scratch or paying whatever they ask. It often appears in subtle ways:

  • The site is built on a closed platform you cannot export from
  • The developer registered your domain in their name
  • Hosting runs only on the developer’s account
  • The contract keeps the code ownership with the developer
  • Key features rely on paid plugins or licenses tied to the developer

Common ownership situations

Template and subscription platforms

With hosted website builders, you typically license the service rather than own the underlying code. You can usually keep your content, but you often cannot export a working copy of the site itself.

Agency or freelancer builds

Ownership depends entirely on the contract. In many arrangements, the developer keeps the rights unless the agreement explicitly transfers them to you, often after final payment. Never assume.

Custom code with full transfer

The cleanest model is a custom build where the contract states that all source code, design assets, and account access transfer to you once the project is paid for. You can then host, edit, or hand the site to another developer freely.

A checklist to protect yourself

  1. Get ownership in writing. The contract should say the code and design assets transfer to you, and when.
  2. Register the domain in your name. You should be the registrant and hold the login.
  3. Own your hosting and key accounts, or have them transferable on request.
  4. Ask for the source code and repository access at handover, not just a live site.
  5. List third-party licenses. Know which paid tools or plugins the site depends on and who pays.
  6. Request documentation covering how to deploy and maintain the site.
  7. Clarify what happens if you leave. There should be no penalty for taking your site elsewhere.

Red flags to watch for

  • “We retain ownership of the code” with no path to transfer
  • The developer insists on keeping your domain or hosting login
  • Reluctance to share the source code at the end
  • A large fee to export or migrate your own site
  • Vague answers about who owns what

    • Why ownership matters for growth

    As your business grows, you may want to change developers, add features, move hosting, or sell the company. Full ownership keeps all of those options open. It also removes the risk of being stranded if a vendor raises prices, changes terms, or shuts down.

    Frequently asked questions

    Do I automatically own my website if I paid for it?

    Not necessarily. Ownership depends on your contract. Without a written clause transferring the code and design to you, the developer may keep the rights. Always confirm ownership in writing.

    What is vendor lock-in in web development?

    Vendor lock-in is when your site depends on a provider’s proprietary platform, hosting, or accounts so that moving elsewhere is costly or impossible.

    What should I receive when my website project is finished?

    You should receive the full source code, design files and assets, and access to or ownership of your domain, hosting, and any related accounts.

    Own what you pay for

    At Caventra, clients own their code, design assets, and accounts once the project is complete, with no lock-in. Learn about our custom web development, see how we work on the process page, or start a project to talk it through.