Who owns the source code in a software contract?
Quick answer
Unless the contract says otherwise, the company that writes the code usually keeps the copyright. Your contract should assign the code, designs and documents to you once the project is paid for, and should list any open-source or paid parts that keep their own licences.
Vastavik Bajpai , Founder
· 2 min read
Owning the code is the difference between owning your software and renting it. It decides whether you can change suppliers, sell the business with its systems intact, or fix a problem yourself. Yet it is the clause most buyers never read.
What the default is
In most countries, the person or company that writes code owns the copyright unless a written agreement says otherwise. Paying for the work is not the same as owning it. That surprises many buyers.
What your contract should say
- The source code, designs, documents and accounts are assigned to you on final payment.
- You receive the code in a form you can use: a repository, written steps to put it live, and the logins.
- Open-source parts keep their own licences, and the contract lists them.
- Any paid component or subscription is named, with its cost.
- The supplier may keep general know-how and reusable tools, but not your specific software.
Three phrases to be careful of
Licence to use. A licence is permission, not ownership. It can be withdrawn or priced. Perpetual licence. Better, but you still cannot change suppliers freely. Ownership on request. Ask what the request costs.
What ownership does not mean
Owning the code does not mean you own the framework it was built on, the hosting, or the AI model it calls. Those belong to their makers and you use them under their terms. Your contract should make the boundary clear.
Our position
You own the full code, designs and documents once the project is paid for. It is written into every quote. See how we work. This guide is general information, not legal advice; ask a lawyer about your own contract.
Questions people ask
Can I ask for the code before the final payment?
You can ask, and many suppliers will share a repository during the build. Ownership normally transfers when the last invoice is paid.
What if the supplier used their own reusable tools?
That is normal. The contract should give you a licence to keep using those tools inside your software, while the supplier keeps the right to reuse them elsewhere.
Do I own the design files too?
Only if the contract says so. Ask for the design files and the brand assets to be included.
Related pages
Pages people read alongside this one.
The service this guide is about
More guides
Custom software or ready-made: which to buy?
Buy ready-made software when it does most of what you need and your process can bend to fit it. Build custom software when your process is the advantage, when several tools no longer talk to each other, or when subscription costs and workarounds are eating the savings.
How do you choose a software development company?
Judge a software company on how it works, not on its sales pitch. Ask who you will actually talk to, how it quotes, whether you own the code, what happens after launch, and ask to speak to a past client. The answers matter more than the size of the company or the length of its client list.
Fixed price or pay by the hour: which is better?
Choose a fixed price when the scope is clear and written down. Choose paying by the hour when the work is genuinely uncertain and you can watch it closely. Most business projects do best with a fixed price per part, which gives you a firm number for what is known and a clear process for what changes.