Материалы журнала опубликованы на английском языке. Русская версия сайта

StrategyOWNERSHIP · CONTRACT · CONTROL

Who Owns the Code? Source Code and IP Ownership in Software Contracts

Paying for software does not make you its owner by default. What a contract should assign, what is only licensed, and how to make sure you control the code, accounts and data.

The short answer

Paying for software does not by itself make you its owner. In many legal systems the party that writes the code owns the copyright until a written agreement transfers it. A sound contract assigns the rights in the deliverables to you on payment, lists what is licensed rather than owned, and puts repositories, cloud accounts, domains and store accounts under your control. This is general information, not legal advice.

Weighing this for your business? Request a project review

Illustration: Who Owns the Code?

Our take

Axiom Forge transfers the rights to deliverables and source files under the contract. Repositories, cloud accounts, domains and production credentials are controlled by you or transferred to you, and handover is discussed before work begins.

Gevorg AntonianFounder & CEO, Axiom Forge
In this article6 sections · 4 min

The default rule surprises most clients

UK government guidance states it plainly: when you commission another person or organisation to create a copyright work, the first legal owner is the creator and not the commissioner, unless you agree otherwise in writing.

United States law reaches a similar place by another route. The US Copyright Office explains that a work by an independent contractor is a “work made for hire” only if it falls into specific statutory categories and the parties agree so in writing. The nine categories do not name software as such, so code written by a contractor will often fall outside them, which is why well-drafted contracts contain an explicit assignment of rights. Copyright law is national, and the details differ from country to country; WIPO publishes a general introduction to copyright.

What the contract should say about each asset

A product is made of several kinds of material, and each needs its own sentence in the contract.

Ownership terms by kind of asset
AssetWhat the contract should say
Custom source codeAssigned to you on payment
Designs and source filesAssigned, with editable files delivered
Open-source componentsListed with their licences
Third-party services and SDKsAccounts in your name; licence terms noted
The supplier’s own tools and librariesLicensed to you permanently for use in the product
Data and contentYours; processing terms defined

Ownership on paper is not control

A clause cannot deploy a product. Control means that your company can open the repository, sign in to the cloud account, renew the domain and publish an update to the app stores without asking anyone.

Open these accounts in your company’s name from the first day and grant the supplier access to them. The reverse arrangement, where the supplier owns the accounts and promises to transfer them later, is a common source of painful separations.

Open source is licensed, not owned

Almost every product contains open-source components. You do not own them; you use them under their licences. Permissive licences ask for little more than attribution. Copyleft licences can require you to publish your own changes, or more, under the same terms.

Ask for a list of the components and their licences; the Open Source Initiative keeps the reference list of approved licences. The list takes a competent team an hour to produce, and it tells you a great deal about how carefully they work.

A handover checklist

Whether a project ends well or badly, the same items should be in your hands.

  • Full source code with its history, in a repository you own
  • Design files in an editable format
  • Access to hosting, domain, analytics and store accounts
  • Credentials and keys, rotated after the handover
  • Build and deployment instructions that a new team can follow
  • A list of third-party services, licences and renewal dates

Red flags

Be careful when a proposal says nothing about ownership, when the rights pass only “on request”, when the supplier insists on hosting everything in its own accounts, or when the product depends on a proprietary framework that only the supplier can maintain.

None of these is always dishonest. Each of them makes it expensive to leave, and that should be your decision, made knowingly.

Discuss your project with the founder

Questions leaders ask

Do I own the code if I paid for it?

Not automatically. In many countries the developer owns the copyright until a written agreement assigns it. Make sure the contract transfers the rights in the deliverables to you on payment.

What is the difference between an assignment and a licence?

An assignment transfers ownership to you. A licence lets you use something that still belongs to someone else. Custom code is usually assigned; open-source components and the supplier’s own libraries are licensed.

Should the developer and cloud accounts be in my name?

Yes. Accounts opened in your company’s name, with access granted to the supplier, keep the product under your control whatever happens to the relationship.

Sources

  1. GOV.UK — Ownership of copyright worksgov.uk (opens in a new tab)
  2. U.S. Copyright Office — Circular 30: Works Made for Hirecopyright.gov (opens in a new tab)
  3. Open Source Initiative — Licensesopensource.org (opens in a new tab)
  4. WIPO — Copyrightwipo.int (opens in a new tab)

How Axiom Forge can help

Turn the guidance into an accountable product plan.

Axiom Forge connects product direction, UX, design and engineering for websites, apps and AI systems. Start with the business outcome, the people who must use the product and the operating constraints behind it.

Founder-led review · NDA on request · No obligation

See services and starting prices

Write to us

Email us — we reply in English, Russian or Armenian.

Our time now:

Analytics preferences

We use Google Analytics and Google Ads to understand which pages help visitors and to measure enquiries. Form contents and personal details are never sent to them.