Who Owns Your Business Website After Development?

2026.11.16
Who Owns Your Business Website After Development?

Who Owns Your Business Website After Development?

Investing in a professional website is a significant decision for any business. You may pay for the design, development, content setup and hosting, but does that mean your company owns everything once the website goes live?

Not necessarily. Website ownership involves several separate elements, including your domain name, hosting account, source code, design assets and content. Each can have different ownership, licensing and access arrangements.

For businesses in New Zealand, understanding these differences before signing a website development agreement can prevent unexpected costs and operational difficulties later.

A website should not only meet your business requirements today. You should also know what happens if you need to update it, change providers or expand its functionality in the future.

1. Who Owns the Domain, Hosting and Website Files?

A business website consists of several components, and paying one agency to manage them does not automatically give you the same rights over every component.

Domain name registration

Your domain name is the address customers use to find your website, such as yourbusiness.co.nz.

Under New Zealand's .nz domain rules, the registered domain holder has the right to use the domain while the registration remains valid. Technically, this is a registration licence rather than permanent ownership of the domain name itself.

The Domain Name Commission recommends that businesses ensure they are recorded as the registrant of their domain.

If a development agency registers the domain on your behalf, your business should confirm that its details appear as the domain holder and that it can manage renewals or transfer registrars when necessary.

Website hosting

Hosting is the infrastructure that makes your website accessible online.

An agency may host your website on its own infrastructure, arrange third-party hosting or set up an account directly under your business.

These arrangements affect how easily you can change providers.

For example, a website hosted in an account controlled entirely by the agency may require assistance to migrate, even if your business has the right to use the website.

It is worth confirming who manages the hosting account, who receives renewal notices and whether website backups can be exported.

Website files and content

Website files can include page layouts, images, stylesheets, scripts, databases and application code.

However, access to those files is different from owning the copyright in them.

Your business might have permission to use a completed website without receiving every editable design file or the original development source code.

These details should be addressed in the development agreement rather than assumed after launch.

2. Does Paying for Website Development Mean You Own the Copyright?

Website copyright is more complicated than a simple distinction between the client and the developer.

In New Zealand, the Copyright Act 1994 contains specific rules for commissioned work.

Section 21 provides that a person who commissions and pays, or agrees to pay, for certain types of work, including computer programs and specified artistic works, is generally the first copyright owner when the work is created under that commission.

However, these provisions are subject to agreements that state otherwise.

Different parts of a website may also fall into different copyright categories.

For example, a website project might involve:

  • Custom software developed specifically for your business
  • Original graphics and interface designs
  • Written content supplied by your company
  • Licensed photographs and illustrations
  • Third-party software, plugins and frameworks
  • Existing code or design components reused by the developer

These components should not automatically be treated as one asset with identical rights.

A development agency may use licensed software or third-party components that cannot be transferred as exclusive intellectual property.

Similarly, purchasing a stock photograph or using a commercial plugin normally provides rights under a particular licence rather than unrestricted ownership.

The practical question is not simply whether your company owns the website. It is what your company is legally permitted to use, modify, reproduce and transfer.

Before development begins, the agreement should identify the rights associated with custom-created work, pre-existing components and licensed materials.

It should also state whether editable design files, source code and database exports are included in the final deliverables.

This allows both the business and the development agency to understand their responsibilities without relying on assumptions.

3. What Happens If You Change Your Website Development Agency?

Businesses sometimes need to change their website provider because of new technical requirements, maintenance costs or changes in internal operations.

Whether the transition is straightforward depends on how the original website was developed and managed.

Consider a New Zealand manufacturing company that commissions a website with product listings, downloadable technical documents and an enquiry form.

After several years, the company wants to introduce a customer portal and integrate its website with an internal management system.

The new development provider may need access to the existing website code, content database, hosting environment and relevant technical documentation.

If these resources are available and the business has the necessary rights, the provider may be able to extend the existing system.

However, if the website was built on a proprietary platform that does not permit source-code access or full data export, the available options may be limited.

The business might need to continue using the original platform, migrate its content to another system or rebuild certain functions.

This does not automatically mean the original agency has acted improperly. Some website services are intentionally offered as managed or subscription-based products rather than transferable custom-developed systems.

The important distinction is whether the business understood those limitations before purchasing the service.

Changing providers may also involve practical issues beyond the website files.

For example, the company may need to transfer DNS management, maintain business email settings, export website content and preserve important page addresses.

If the existing website receives enquiries through search engines, changes to URLs should be planned carefully. Relevant redirects and content migration can help reduce avoidable disruption.

A smooth agency transition depends on technical access, contractual rights and a documented handover process.

These are matters worth considering even when there is no immediate intention to change providers.

4. What Should You Confirm Before Signing a Website Contract?

A website development agreement should explain more than the initial design and development cost.

Before approving a project, businesses should clarify several practical arrangements.

Domain registration and hosting access

Confirm whose name will appear as the domain holder, who manages the hosting service and how the business can access or transfer those services.

Source code and design deliverables

Check whether the final handover includes the website's deployable files, custom source code, editable design files and technical documentation.

For projects involving custom functions, clarify whether the delivered code can be maintained or modified by another developer.

Third-party software and licences

Identify important commercial plugins, themes, fonts, stock images and external services.

The agreement should explain any ongoing licence costs and whether those services can continue to be used after the development relationship ends.

Content and data access

Businesses should understand how website content, enquiry records and other relevant information can be accessed or exported.

For websites that store customer information, appropriate access controls, secure handling and data retention arrangements should also be considered.

Maintenance and future development

Confirm what happens after launch.

Some agencies include an initial period for correcting agreed-scope defects, while content changes, feature additions and ongoing maintenance may be charged separately.

It is also useful to determine whether the business can appoint another provider to carry out future updates.

These points do not necessarily need to result in full ownership of every component.

For example, a business may prefer a managed website platform because the provider handles hosting, updates and technical maintenance.

That arrangement can work well if its features, costs, limitations and exit options are understood from the beginning.

A custom-developed website may provide different levels of control and flexibility, but the actual rights and deliverables still depend on the project and its agreement.

Final Thoughts

Owning a business website is not the same as having complete control over every file, service and technology used to operate it.

For New Zealand businesses, domain registration, hosting arrangements, copyright ownership, software licences and access to development files should be considered separately.

Before commissioning a website, confirm what will be delivered, which rights your business will hold and how the website can be maintained or transferred in the future.

A clearly defined development agreement helps businesses make informed decisions and reduces uncertainty as their website requirements change.

For businesses planning a new website or a more advanced digital platform, considering long-term management requirements at the beginning can be just as valuable as choosing the right design.

Frequently asked questions

Should my business be registered as the domain holder?

The Domain Name Commission recommends that businesses ensure they are recorded as the registrant of their domain. If a development agency registers the domain on your behalf, your business should confirm that its details appear as the domain holder and that it can manage renewals or transfer registrars when necessary.

Does paying for website development give my business copyright ownership?

Section 21 provides that a person who commissions and pays, or agrees to pay, for certain types of work, including computer programs and specified artistic works, is generally the first copyright owner when the work is created under that commission. However, these provisions are subject to agreements that state otherwise. Different parts of a website may also fall into different copyright categories.

Will my business receive the source code and editable design files?

Your business might have permission to use a completed website without receiving every editable design file or the original development source code. These details should be addressed in the development agreement rather than assumed after launch.

What access might a new website development provider need?

The new development provider may need access to the existing website code, content database, hosting environment and relevant technical documentation. If these resources are available and the business has the necessary rights, the provider may be able to extend the existing system.

What should a website agreement explain about third-party licences?

The agreement should explain any ongoing licence costs and whether those services can continue to be used after the development relationship ends.

Plan the present.
Build the future.

Start a project