Owning your content is not owning your website. The three layers of ownership, how hosted and AI builders handle each, and six questions to ask first.
The question nobody asks until it hurts
Most business owners find out who owns their website the day they try to leave. The agency that built it has gone quiet. The builder subscription has doubled. A developer quotes a rebuild because there is nothing to hand over. The terms of service always said how it worked, and nobody read them, because the question sounded paranoid when the site was new.
It is not paranoid. A website is the one marketing asset that compounds for years, and whether you can take it with you decides whether that compounding belongs to you or to a vendor. This guide separates the layers of ownership, explains how the common options handle each one, and gives you the six questions to ask before you build or rebuild.
Three layers of ownership
"Do I own my website" is really three questions, and the answers are usually different.
- Content. The words, images, logo and data. On almost every platform you own these. You can usually export text and images, though the export is often a pile of files rather than a working site.
- Design and structure. The templates, layouts, components and the way pages fit together. On hosted builders this belongs to the platform. You licensed the use of it while you pay. It does not leave with you.
- Code and infrastructure. The source files that produce the site, the repository they live in, the hosting account and the domain. This is the layer that determines whether a developer can pick up where the vendor left off. On most platforms there is no code to own because the site only exists inside the platform's system.
When a vendor says "you own your website", they almost always mean the first layer. When a developer says it, they mean the third. The gap between the two is where the lock-in lives.
How the common options compare
Hosted builders such as Wix, Squarespace and Shopify give you the content layer and rent you the other two. The trade is honest and often worth it: hosting, security, templates and a visual editor for a monthly fee. But there is no export that yields a working site, because the site is a configuration inside their system, not a set of files. Leaving means rebuilding.
WordPress sits in the middle. The code is open source and you can move it between hosts, which is real ownership of the third layer. In practice the site depends on a theme and a stack of plugins, each on its own license and update cycle, and the portability is only as good as the person maintaining it.
Agency-built custom sites vary completely by contract. Some agencies hand over a repository and transfer the hosting account at the end of the project. Others host it themselves, keep the code private and charge a retainer for changes. The deliverable is in the contract, and if the contract does not name a repository and an account transfer, assume you will not get them.
AI website builders are the newest and the least consistent. All of them generate real code, which is a step forward. Some keep that code inside their own hosting and editor, so you have the same relationship as with a hosted builder, just faster. Others sync the code to a repository in your GitHub and can deploy to hosting in your name, which is ownership of the third layer. The difference is not visible in the demo. You find it under Settings, or in the terms, or by asking.
Six questions to ask before you build
- Where does the source code live, and in whose account? The right answer names a repository in your GitHub, GitLab or equivalent, not a workspace inside the product.
- Where is the site hosted, and in whose account? A project in your Vercel, Netlify, AWS or similar account. If the hosting is only theirs, ask what happens when you stop paying.
- What framework is the output? A standard framework such as Next.js means any developer can work on it. A proprietary format means only the vendor can.
- Can I export a working site today, and have you tried it? Ask them to show you the export running somewhere else. An export that only produces HTML snapshots is content, not a site.
- Who owns the domain and the DNS? Always you, at a registrar in your name. Never let a vendor register it for you.
- What exactly stops working if I cancel? The honest answer lists the editor and the AI features, and confirms that the published site, the code and the leads remain yours.
Write the answers into the contract or save the support reply. The vendor that answers these six plainly is the one you can trust with the other things too.
What real ownership looks like day to day
It is less dramatic than it sounds. A repository in your GitHub account with a commit for every version of the site, which you may never open but a developer can. A project in your Vercel account where the site is deployed, with your domain attached and the DNS at your registrar. A contact form whose submissions land in a system you can export from. A builder or an editor you use because it is convenient, not because the site cannot exist without it.
The test is simple. If the builder disappeared tomorrow, would the site still be live, and could a developer you hire the following week make a change to it? If both answers are yes, you own your website. If either is no, you are renting it, and the rent is not the subscription fee. It is the rebuild you will pay for later.
How Brainito handles it
We built the Website Builder around the third layer because the first two were already solved. The output is a standard Next.js project. Every version is pushed to a private repository in your own GitHub account, and publishing deploys it to a project in your own Vercel account, with your domain attached through DNS records you add at your registrar. You connect both once under Settings. Leads from the site's forms save to your Brainito contacts, which export.
If you stop using Brainito, the repository, the Vercel project, the domain and the live site stay exactly where they are, because they were never ours. What you lose is the editor, the chat and the generated images. That is the arrangement we would want as customers, and it is the one we think every builder should be asked for. If you are weighing AI builders against each other, our comparison with Lovable goes through where the code and hosting end up on each.