When a website is delivered, the question “Who owns it?” can refer to several different things: the domain name, source code, visual assets, written content, hosting account, customer data, and third-party licenses. These may be governed by different accounts, contracts, or terms. Before development begins, list each component and agree who controls it, what rights are transferred, and how access will be handed over.
1. Domain registration
The domain is the address people use to reach the website. Confirm whose account registers it, who pays renewal charges, which email receives renewal notices, and who can change DNS settings. The business should understand how to access and renew its domain. Avoid leaving a critical domain dependent on an individual account that the business cannot access.
2. Source code and repository
Source code is the material used to build and maintain the website. Ask whether the project includes a repository, how access is granted, what files and build instructions are provided, and whether any components are subject to third-party licenses. Ownership or usage rights depend on the agreement and applicable law, so define the deliverable, permissions, and transfer terms in writing rather than assuming that payment automatically settles every detail.
3. Design assets and content
Logos, photographs, illustrations, fonts, copy, icons, and templates may have different ownership or licensing conditions. Ask which materials are original, which are licensed, whether licences can be transferred, and what restrictions apply. Keep records of asset sources and relevant licenses. Do not assume that every stock asset or paid font can be redistributed freely.
4. Hosting and infrastructure
Hosting is where the website's files or application are served. Confirm who owns or controls the hosting account, whether the site can be transferred, which services cost extra, and what backups exist. For platforms with separate frontend, backend, database, and email services, document each component independently. Some sites cannot be moved simply by copying a folder because they depend on databases or third-party services.
5. Analytics and third-party accounts
Analytics, email delivery, forms, customer-management tools, payment providers, and other integrations should have clearly identified account owners and administrators. Use business-controlled accounts where appropriate and grant providers the access they need. Keep a list of active subscriptions, renewal dates, integration dependencies, and revocation steps for when a relationship ends.
6. Credentials and security
Use a password manager, unique credentials, multi-factor authentication where supported, and role-appropriate access. Do not exchange long-lived passwords casually in chat or embed secrets in source code. At handover, rotate credentials where appropriate, remove unnecessary access, verify the remaining administrator accounts, and record who is responsible for future changes.
7. What should the handover include?
A practical handover checklist may include repository access, deployment instructions, a list of domains and services, ownership and license records, admin account information transferred securely, backups where applicable, environment setup instructions, integration documentation, and the support agreement. Confirm that the site can be built or maintained by an appropriately skilled person and that critical renewal notifications reach the business.
8. Put the terms in the agreement
The contract should identify the deliverables, rights transferred or licensed, third-party components, payment conditions related to transfer, access arrangements, confidentiality, support, and any limitations. If the website handles sensitive data or supports an important business process, obtain qualified legal and technical advice on the specific arrangement.
Conclusion
A website is easier to operate when the business knows who controls every important component. Before approving a proposal, clarify domain control, code and asset rights, hosting, third-party accounts, access, and handover. Written clarity protects the client and gives the development provider an unambiguous delivery target.
Frequently Asked Questions
Does paying for a website automatically transfer the source code?
Not necessarily in every situation. The agreement, deliverables, licenses, and applicable law determine what rights are transferred. Confirm the terms in writing.
Should the client own the domain account?
The business should have clear control over its domain and renewal process. Account ownership and administrative access should be explicitly agreed.
What should be included in website handover?
Depending on the project, handover may include source code, repository access, deployment instructions, account ownership details, licensed-asset records, backups, integration documentation, and support terms.
Ready to Build or Upgrade Your Website?
At Caventra, client ownership is a foundational principle: 100% full source code ownership, zero proprietary lock-in, and all accounts registered in your name. Learn more about our Clean Code Architecture, our managed Website Maintenance, or get in touch with our team.