Skip to content

What you actually own when the website project ends

Domain, hosting, source code, design files, content. Who holds what at handover decides whether you own a business asset or a subscription to your developer.

Vins Creatives

3 min readProcess

The end of a website project is where the quiet problems surface. Everything works, everyone is pleased, and nobody has said out loud who holds the keys. Six months later you want to change agency and find out.

Here is the full list of what exists at the end of a build, and what "you own it" has to mean for each one.

The domain

What it is: your address. Also, usually, your email.

What ownership means: it is registered to your name or your company, you hold the registrar login, and you can transfer it without anyone's permission.

This is the one that ruins people. A domain in a developer's account is not yours in any sense that matters, and the moment of discovery is always the worst possible moment — a dispute, a disappearance, or an unpaid invoice from someone who now controls your email.

Check it yourself: a WHOIS lookup takes ten seconds and shows you the registrant.

The hosting

What it is: the machine your site runs on.

What ownership means: the account is in your name and billed to you, or you can move away without asking.

Reseller hosting is fine if it is explicit. It becomes a trap when it is silent — you cannot take a backup, cannot see the logs, and cannot migrate without cooperation.

The source code

What it is: the actual site, as a developer works on it.

What ownership means: it is in a repository you can access, and the contract says the copyright transfers to you on final payment.

That last clause matters more than people expect. Under default copyright, whoever writes something owns it unless there is an agreement saying otherwise. No agreement means your developer owns your website, however much you paid.

We hand over the repository at launch along with a written runbook, because a repository nobody can run is a filing cabinet.

The design files

What it is: the Figma or Illustrator files behind the screens.

What ownership means: you can open them, and you can give them to somebody else.

Often skipped, always missed later. The day you need one more page in the same style, the difference between having the design file and not having it is a few hours versus a redesign.

The content

What it is: your words, your photographs, your logo.

What ownership means: you own what you supplied, and you have a licence for anything bought on your behalf.

Watch the stock images. If your designer used a photo under their own subscription, that licence may not cover you, and it certainly does not cover you after they stop paying for it. Ask which images are licensed and to whom.

The analytics

What it is: everything you will ever know about who visits.

What ownership means: the property is in your account, and you are an owner rather than a viewer.

Analytics set up under an agency account is data you lose access to the day the relationship ends — including all the history, which is the only part that is irreplaceable.

Every item on this list is free to get right at the start of a project and expensive to fix at the end. None of it requires trust. It requires writing it down.

The two-line version

Ask for one document, before you pay a deposit, listing:

  1. Every account that will exist, and whose name it is in.
  2. Everything that transfers to you at final payment.

Any competent studio can produce that in an afternoon. Anyone who will not is telling you something.

Start a project

Book a call. We will tell you what we would actually do, what it costs and how long it takes — before anyone signs anything.