Who owns the code of custom software? What belongs in your contract

Who owns the code and the data when you have software built? A practical checklist for your contract: ownership, exit, support, licences and extra work.

In short

If you have custom software built, you do not automatically own the code: without a written agreement, the copyright in principle stays with whoever wrote the code. So set out in your contract who owns the code and the data, how you get them if you leave, which third-party licences are included, which response times apply and how extra work is charged. At Aziri, the code we write for you and your data are yours; if part runs on a third-party platform, that is stated in the proposal beforehand.

If you have custom software built, you do not automatically own the code. Software falls under copyright, and without a written agreement the rights in principle stay with whoever wrote the code. So what is in your contract determines whether you can later continue with another party, or are stuck.

At Aziri, the code we write for a customer and all their data belong to the customer. If part runs on a third-party platform, that is stated in the proposal beforehand, together with how a handover then works. Below is what we think belongs in every contract for custom software, whether you work with us or with someone else. It is not legal advice, but a checklist to put next to a quote.

Who owns the code when you have software built?

The code belongs to whoever the contract says. European law protects computer programs through copyright (Directive 2009/24/EC). In Belgium, with an external developer that right does not automatically pass to the client. If nothing is in your contract, you have at most a right of use, and it is unclear what you may have changed.

There are two common forms:

  • Transfer: the rights to the code written for you pass to you. You can have it changed by whoever you want.
  • Broad licence: the builder keeps the rights, but you may use the code without limits, have it changed and have it taken over.

Note the difference between code written specifically for you and components the builder uses for several customers, such as their own library or a base platform. For the latter you usually get a right of use. That is normal, as long as you know which components they are and what happens if you leave.

Who owns the data?

The data you enter into the software belongs to you, and that should be in black and white in the contract. Also ask in what form you get it: a full export of the database in an open format is something different from a few CSV files.

If the software processes personal data of your customers or employees, the builder or the host is a processor, and you need a data processing agreement (Article 28 of the GDPR). It states where the data is stored, who can access it and what happens when the collaboration ends. For cloud services, the European Data Act also sets rules on switching to another provider (Regulation 2023/2854).

What belongs in your contract for custom software?

These are the points we want to see in every contract, with the question you can ask alongside:

Topic What you set out Question for your builder
Ownership of code Transfer or broad licence for the code written for you May another party change the code?
Ownership of data The data is yours, with a full export In what format do I get my database?
Exit and handover What you get when you leave: code, database, documentation, access How fast and at what cost?
Third-party licences Which platforms, libraries and services are included, and who pays for them What happens if those prices rise?
Hosting and security Where it runs, backups, who has access How often is there a backup, and has it been tested?
Support Response times per priority, and what is not covered by support What is critical, and who decides that?
Extra work How new requests are priced and approved What is not in the scope?
Delivery and aftercare When something is finished, and how long bugs are fixed at no extra cost How do I test with real data?

What if your builder stops or you want to switch?

Then you want three things: the source code, the database and enough explanation for another developer to continue with it. Set out in your contract that you can request these at any time, and not only in case of bankruptcy. An exit clause stating what you get, in what form and within what period, prevents discussion at the moment you can least use it.

For large or critical applications you can also have the code held by a third party, who releases it if the builder does not meet their obligations. For most of our customers’ applications that is not necessary, because the code and the data are already theirs.

If your supplier builds on a third-party platform, also ask what happens to that platform’s licence if you leave. Sometimes you can take the application to your own account, sometimes not.

Which response times are normal?

Response times are agreed per priority, and the clock runs during support hours. With us, the response times per priority are in the proposal, so you know in advance where you stand.

A response time is not a resolution time, and we would read a contract that promises a resolution time for every problem with suspicion. Also ask what falls outside support. With us, that includes new features and training. If an integration breaks because of a change in someone else’s software, we follow it up via support, but we agree rework on the side of that package with you beforehand.

How do you avoid discussions about extra work?

Extra work almost always arises where the scope was vague. That is why we work with a scope you approve before we build, and preferably with one fixed price upfront for analysis, build, testing and delivery. What has not been discussed is not included, and that is also stated in the proposal.

What you put in the contract:

  • How a new request is priced: a fixed price per change or per hour?
  • Who approves extra work before it is started.
  • What happens to the budget if you change the scope during the build.

Weekly demos help here more than any article, because then you see every week what is being built and you adjust before it gets expensive. How that works with us is explained under our approach. What a project roughly costs is on what custom software costs, and whether custom software is the right choice at all is covered in Custom or standard software?.

Frequently asked questions

Do I automatically own the software I have built?

No, not automatically. Software is protected by copyright, and with an external builder those rights in principle stay with whoever wrote the code, unless the contract transfers them. So have the transfer or the right of use set out in writing.

What if my software builder stops or goes bankrupt?

Then you want the source code, the database and the documentation, and another party that can continue with them. Agree in your contract that you can request them at any time, or have them held in escrow by a third party. At Aziri, the code we write for you and your data are yours; if part runs on a third-party platform, that is stated in the proposal beforehand.

What is the difference between response time and resolution time?

Response time is the time until someone picks up your report; resolution time is the time until the problem is gone. Most contracts, ours included, guarantee a response time, because the resolution time depends on what goes wrong.

Why do I pay a licence for software I had built myself?

The licence usually covers what keeps running after delivery: hosting, secure access, backups, updates and basic support. At Aziri it is separate from the build price, from €1,000 per year.

Is this legal advice?

No. This is a practical checklist based on what we see in contracts. Always have a contract with large amounts or sensitive data reviewed by a lawyer.

Maxim Daels

Maxim DaelsSales Manager, Aziri

Maxim Daels works at Aziri (Sales Manager).

Is this where you get stuck?

Tell us in a half-hour call how things run today. You get an honest assessment, even if the answer is that you do not need custom software.

We reply quickly.