Who should own your website’s code, domain and accounts?

Why ownership matters

A website depends on several accounts: the domain, the hosting, the code, analytics, email. If those sit in a supplier’s name, changing supplier or even making a small update can turn into a negotiation.

Our rule is simple: code, credentials and accounts are handed over to you. No lock-in.

The ownership checklist

• Domain name: registered in your company’s name, with you holding the login.
• Hosting or cloud account: billed to you, with your team as the account owner.
• Source code: in a repository you own or receive in full at handover.
• Admin logins: for the CMS, store or app, with your own administrator account.
• Analytics and Search Console: your property, with us added as a user.
• Third-party services: payment gateways, email and form services in your name.

Access, not ownership, for suppliers

Agencies and developers need access to do their work, and that’s fine, as users you add, not as owners. When a project ends, you remove their access and nothing breaks.

What a proper handover includes

1. The full source code and any build instructions.
2. Every login and API key, moved to accounts you control.
3. Notes on how the site or app is deployed and updated.
4. A list of the services it depends on and what each one costs.

With that in hand, you can keep working with us, bring the work in-house or move to someone else. The choice stays yours.