Custom software · 4 min read

Why you should own your software.

You pay for the development, so the software is yours. Right? Not necessarily. In this article you read why ownership matters and what to arrange properly in advance.

Bastiaan Meijer · CareScript

Paying is not the same as owning

Under Dutch law, copyright in software in principle lies with whoever made it. A transfer of that right must be set out in writing. Similar rules apply in many other countries. Without proper agreements you may therefore only have a right of use, even though you paid for the development in full.

Why it matters

  • Freedom: you decide who maintains or extends the software.
  • Continuity: if a supplier stops, you can carry on.
  • Value: software you own counts towards the value of your organisation.
  • Control over data: you decide where your data is stored and who can access it.

More than just rights

Ownership on paper is one thing. In practice you also want to actually have:

  • The source code, with full history, in a repository in your name.
  • The accounts for hosting, domains, app stores and external services.
  • The keys and passwords, securely managed and transferable.
  • The documentation, so another team can carry on with it.

What to agree in advance

  1. Transfer of the intellectual property rights to you.
  2. Source code in your own repository, from day one.
  3. Hosting and accounts in your organisation's name.
  4. Documentation as part of the delivery.
  5. Clear agreements on third-party components, such as open-source libraries and their licences.

How CareScript arranges this

At CareScript, ownership is the starting point. Source code, data and accounts are in your name from the start and the rights are transferred to you. You can have us do the maintenance, but you do not have to. That way you are never dependent on a single supplier.

Further on this topic

AI employee portal development

Read how CareScript can help you with this, or book a no-obligation call straight away.