Who owns the source code of your application?
Source code is the written set of instructions a program is built from. Who holds the rights to it decides whether tomorrow you can change provider, bring in another team or sell the company with its software inside.
1What source code is
It is text that programmers read. What you see on screen is the result of running it. For example, the rule “if an invoice falls due in under seven days, alert accounts” is written in a file somewhere, in a programming language. Without the source code you can use the application, but you cannot change it.
Alongside the code there are other pieces that matter just as much: the database structure, the scripts that install the application on a server, the configuration and the documentation.
2Licence to use or assignment of rights
They are two different things. With a licence to use, you may use the program, but the provider remains the rights holder and can sell the same thing to others. With an assignment of exploitation rights, rights such as reproducing, modifying or distributing the program are transferred to you; the assignment may or may not be exclusive, and has a scope and a duration.
In Spain, computer programs are protected under the Intellectual Property Act. Depending on how it is interpreted in each case, if the contract says nothing clear, the rights could remain with whoever wrote the code even if you paid for the work. That interpretation is for your adviser. We go through the specific clauses in our guide on what to ask for in a development contract.
3What belongs to no one exclusively
No application is written entirely from scratch. It uses third-party libraries and tools, many of them open source, such as Next.js or Postgres. Each has its own licence (MIT, Apache, GPL and others): you can use them on that licence’s terms, but nobody can assign them to you. Some licences carry obligations, such as publishing your changes if you distribute the program.
Nor are external services assigned, such as a payment gateway, which come with their own contract, or the generic components a provider reuses across projects, for which a licence is the norm. What matters is that it is written down what is exclusively yours and what is not.
4What you should receive at the end
Code lives in a repository: an archive with its full history of changes, on services such as GitHub or GitLab. If the repository sits in the provider’s account, you depend on them for access. The simplest approach is to create it from day one in your company’s account and invite the provider. At the end, check that you have:
- Administrator access to the repository, with the full history.
- Instructions to install the application from scratch on a new server.
- The database structure and a way to export the data.
- The list of third-party dependencies and their licences.
- Cloud, domain and app store accounts in your company’s name.
5Our own pieces and third-party pieces in our projects

Certia Group website
New corporate website for an infrastructure engineering firm
We rebuilt Certia Group’s website on Next.js, GSAP and Lenis: third-party libraries, each with its own licence, that no client receives exclusively. It is a review version; the company’s domain still points to the previous site.
Review version. The company’s domain still points to the previous site.

Hopp
Internships for students, one swipe away
An iPhone app with a Supabase backend: besides the code there are developer and server accounts that should be in the rights holder’s name. Hopp is our own product, so they are in the group’s name. Submitted to the App Store in October 2026.
Submitted to the App Store in October 2026
6Frequently asked questions
If I pay for the development, is the code mine?
Not necessarily. Paying is not the same as receiving the rights: it depends on what the contract says. Ask for it in writing and have your adviser review it.
Is a ZIP file at the end enough?
It is better than nothing, but without the history and installation instructions another team will struggle to pick it up. Ask for repository access and documentation good enough for anyone to install it.
What happens to open-source libraries if the code is mine?
They still belong to their authors, under their licence. What is yours is what was written for you on top of them.
Do you hand over the code?
We propose that the repository is in the client’s name from the start, and we put it in writing for every engagement. Our published projects are mostly the group’s own products, so we do not yet have a published case of handing code over to a client.
Do you know whose name your repository is in?
We will help you take stock of what you have: code, accounts, domain and services, and whose name each one is in.
Tell us your problem