Skip to content
All insights
Insight

Who should own the source code, hosting and software accounts?

A practical guide to source code, domain, hosting and software account ownership for businesses commissioning websites, apps and custom software.

By Syed Aalishan Asghar · 30 September 2026 · 8 min read

A business should be able to operate, maintain and move its website or software without depending on one supplier for access. That starts with clear ownership of source code, domains, hosting, data and the accounts that keep the service running.

1. Keep business accounts in the business name

Domain registration, hosting, analytics, app stores, payment services and email delivery should normally sit in accounts controlled by the client. A developer can be given the access needed to work without becoming the permanent owner.

This keeps billing visible, makes staff changes manageable and prevents a routine handover from becoming an account recovery exercise.

Use a durable company email address for the primary owner and keep recovery details current. An employee or agency address can be added as an administrator, but it should not be the only route into a critical service.

2. Source code needs a durable home

The repository should live in an organisation or account the client can access. It should contain the current code, a useful history of changes and instructions for running and deploying the project. Sending a zip file at the end is not the same as maintaining a proper repository.

Confirm that the repository includes every component required to build the product, subject to legitimate third-party licences. Deployment settings and secrets should be documented securely rather than committed directly into the code.

3. Domains, hosting and data need separate attention

The domain is often the most business-critical digital asset because it controls the website address and may also control email. The company should be the registrant, know the renewal date and have access to domain and DNS management. Losing hosting is disruptive; losing control of the domain can affect the entire business identity.

Hosting ownership should include visibility of billing, service limits, backups and the region where data is stored. For applications, clarify who owns the production database and how the business can receive a usable export if the supplier changes.

4. Access should be deliberate

Not every person needs full administrative access. Give each supplier and team member the minimum role required, use individual logins where possible and remove access when an engagement ends.

  • Use a shared password manager for credentials that cannot have separate users
  • Turn on multi-factor authentication for critical services
  • Record recovery methods and billing contacts
  • Review access at launch and at the end of support agreements

5. Understand intellectual property and licences

Owning custom source code does not mean owning every component inside a product. Open-source packages, fonts, stock media, APIs and commercial libraries come with their own licences. The contract should distinguish newly created work from pre-existing tools and third-party materials.

The client should receive the rights needed to use, modify and maintain the delivered product. Any restriction that could prevent another developer from continuing the work should be explained before the project starts.

6. Make handover part of delivery

Ownership should be agreed before development starts and verified before final sign-off. A handover checklist should cover code, credentials, documentation, backups, licences and outstanding recurring costs.

Test the handover instead of assuming it is complete. A responsible person on the client side should confirm access to each account, repository and backup. Documentation should be clear enough for a qualified replacement supplier to understand how the service is built and released.

7. Review ownership throughout the relationship

Ownership is not a one-time administrative task. Review account access when team members change, when support agreements end and when new services are introduced. Keep an inventory of critical systems, owners, renewal dates and recovery contacts.

A good supplier should be able to work efficiently without holding the client hostage. Clear ownership protects continuity while still allowing developers and agencies the access they need to support the product properly.

Syed Aalishan Asghar

Founder and Delivery Lead at aaliSoft

Start a conversation

Bring us the problem. We will help shape the right product.

Tell us what you are building and where it currently stands. We reply within one business day, anywhere in the world.

Websites · SaaS · Mobile apps · Games

Discuss your project
(opens in a new tab)