Build log/Working with us

Who owns the code when you commission software in the UK

Under UK law the developer, or the agency that employs them, owns the copyright in code until it is assigned to you in writing. Here is what to put in the contract.

The short answer

  • Under the Copyright, Designs and Patents Act 1988, copyright in code belongs to the person who wrote it, or to their employer, unless it is assigned in writing.
  • An agency or freelancer you hire is not your employee, so paying for software does not by itself make you the owner of its copyright.
  • A good contract assigns the bespoke code to you, licenses any reusable components, lists open-source licences and puts every account in your company’s name.

When you commission software in the UK, the copyright in the code belongs to whoever wrote it, or to their employer, until it is assigned to you in a signed written document. Copyright is the legal right to copy, change and distribute a work, and the Copyright, Designs and Patents Act 1988 treats computer programs as literary works, so the same rules apply to code as to a book. If your contract with an agency or freelancer says nothing about ownership, you have paid for the software without owning it.

The default rule under UK copyright law

The Copyright, Designs and Patents Act 1988 (CDPA) protects computer programs, and the preparatory design material for them, as literary works. The first owner of copyright is the author, meaning the person who created the work. There is one important exception. When an employee writes code in the course of their employment, their employer owns it, unless they have agreed otherwise.

That exception is why ownership catches people out. A developer on your payroll writes code that your company owns automatically. A developer at an agency writes code that the agency owns, because the developer is the agency’s employee and not yours. A freelancer working on their own account owns what they write personally. In both of the last two cases, the work only becomes yours if the copyright is assigned to you.

An assignment of copyright has no effect unless it is in writing and signed by or on behalf of the person transferring it. An invoice marked “paid” does not meet that test, and neither does a conversation in which the agency said “of course it’s yours”.

What happens if the contract says nothing

Without a written assignment you are not left with nothing. A court is likely to find that you have at least an implied licence to use the software for the purpose it was commissioned, and in some cases courts have gone further and found that the client owns the work in equity. Both outcomes depend on the facts, and finding out means a dispute with legal fees on both sides.

An implied licence is also narrower than ownership. It may let you run the software without letting you license it to others, sell it with your business or stop the developer reusing the same code for a competitor. Investors and buyers check intellectual property during due diligence, and a gap here can hold up a funding round or a sale.

Assignment and licence compared

An assignment transfers ownership of the copyright to you. A licence is permission to use something that someone else continues to own. Most commissioned software involves both, because an agency will assign the code it writes for you and license the parts it brought with it.

QuestionAssignmentLicence
Who owns the copyrightYouThe supplier, or the original author
Can the supplier reuse the code for other clientsNo, unless you license it backYes, unless the licence is exclusive
Can you change it and hire another developerYesOnly if the licence allows it
Can it pass to a buyer if you sell the businessYesOnly if the licence allows transfer
Formal requirementIn writing, signed by the supplierBest in writing; an exclusive licence must be in writing and signed
Typical useCode written specifically for youThe supplier’s existing tools, libraries and templates

Background code, open source and third-party services

Not everything in your software can be assigned to you. Most applications contain three kinds of code that someone else owns.

The supplier’s background code

Agencies reuse their own libraries, starter templates and internal tools across projects, and it is reasonable for them to keep ownership of these. What you need is a licence to use them as part of your software that is perpetual, irrevocable, royalty-free and transferable, and that lets another developer maintain them after the relationship ends. Ask for the background code to be identified, so you know where the line sits.

Open-source components

Almost every application depends on open-source packages. Their authors keep the copyright and grant everyone a licence. Permissive licences such as MIT and Apache 2.0 mainly ask for the copyright notice and licence text to be kept. Copyleft licences such as the GPL can require you to make your own source code available if you distribute software that includes the component, and the AGPL can extend that duty to modified software that people use over a network. A supplier should list every open-source component with its licence, and agree with you in advance which licences are acceptable.

Third-party services

Payments through Stripe, maps from Google, email sending and AI models are services you use under each provider’s terms. You never own them. What you should own is the account, so the contract with the provider is between your company and them, and nobody can switch it off by walking away.

What to put in the contract

These are the clauses we’d expect to see in a UK software development agreement. Treat them as a checklist for a conversation with your solicitor. This article explains the general position and is not legal advice, so take advice on your own contract, especially if the software is central to the value of your business.

  1. Assignment of the deliverables. The supplier assigns to you all intellectual property in the code, designs and documentation created for the project. Wording that assigns future copyright as it is created avoids a gap between the work being written and a later signature. The clause should cover everything delivered, however it was produced, including code written with AI tools, where the law on ownership is less settled.
  2. Timing. Agencies often assign on payment. That is fair, as long as each payment transfers the work it covers and ownership does not wait for the final invoice.
  3. Background licence. A perpetual, irrevocable, royalty-free licence to any background code built into the deliverables, which you can pass on if you sell the business.
  4. Subcontractors. The supplier confirms it has written assignments from everyone else who worked on the project, including freelancers. An agency cannot assign rights it never acquired.
  5. Open source. A list of components and licences, and a commitment not to include copyleft code without your written approval.
  6. Moral rights. In the UK, the moral rights to be named as author and to object to derogatory treatment do not apply to computer programs. They do apply to designs, illustrations and written content, so the contract should include a waiver for those.
  7. Non-infringement. A warranty that the deliverables do not infringe anyone else’s rights, with an indemnity if they do.
  8. Handover. Delivery of the full source code with its history, and all credentials, at the end of the project or on termination.

Raise ownership in your first conversation with any supplier. It is one of the questions in our guide on how to brief an agency.

Repositories and accounts in your name

Owning the copyright is of limited use if you cannot get at the code. Ownership on paper and control in practice are separate questions, and the second is settled by whose name is on each account.

  • The source code repository, in an organisation on GitHub, GitLab or Bitbucket that your company controls, with the supplier invited as members.
  • The Apple Developer Program and Google Play Console accounts, enrolled as your organisation. Both ask an organisation for a D-U-N-S Number, which can take a while to obtain, so start early.
  • The domain name, DNS and email, registered to your company.
  • Cloud hosting, databases and backups, billed to your company.
  • Payment, email, SMS, maps and AI provider accounts.
  • Design files and brand assets.

If an app is published under the supplier’s developer account, moving it later is possible on both stores, but it involves a formal transfer with conditions attached. Our handover checklist covers the rest of what you should receive.

Commissioning software? Ask any supplier, including us, to show you the ownership clause before you sign. Talk to us about your project.

Questions people ask

Do I own the code if I paid for it?

Not automatically. Under UK law, payment does not transfer copyright, and an assignment has to be in writing and signed by the supplier. Without one you probably have a licence to use the software, while the supplier or the individual developer still owns it.

Can a freelancer reuse code they wrote for me?

If they still own the copyright, yes, unless your contract restricts it. Once the copyright is assigned to you, they need your permission to reuse that code. General skills and know-how stay with the developer either way.

Who owns code my employee writes?

Your company does, if the employee wrote it in the course of their employment and nothing in their contract says otherwise. Code written by a director who is not an employee, or by a co-founder before the company existed, is a different matter and should be assigned to the company in writing.

Does an agency’s standard contract usually cover ownership?

Some do and some don’t, and the wording varies widely. Read the intellectual property clause before signing, check that it assigns the bespoke work to you instead of only licensing it, and ask a solicitor to review it if the software matters to the value of your business.

Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.