Who owns your software? Code, access and data: what to ask before you sign
Website, online store or management software: if you change supplier, what are you left holding? The questions to ask before you start, so you don't get stuck later.
It is a question almost nobody asks at the start and everybody asks on the day they want to change something: if this relationship ends, what am I left with? The answer depends on agreements made before, not after.
The five things that must stay with you
- The domain, registered in your company's name and not the supplier's.
- The access credentials: hosting, accounts for the connected services, admin panels.
- The code of what was built for you, in a form another developer can pick up.
- The data: customers, orders, content, exportable in a readable format.
- The documentation, the minimum needed to understand how it is made and how to get it running.
Where the lock-in comes from
It is rarely bad faith. More often it is habit: the domain registered “for convenience” in the name of whoever built the site, the hosting on a shared account, a closed platform from which content cannot be exported. As long as the relationship works you don't notice; the problem emerges when you want to move.
This is not legal advice
Here you'll find practical criteria, not professional advice: who holds the rights to code and data depends on what is written in the contract. Have it read by a professional if the project is important.
The questions to ask before you sign
- In whose name are the domain and hosting registered?
- At the end of the project, do I receive the code? In what form?
- Are there components with a paid licence or tied to the supplier?
- Can I export my data whenever I want, and in what format?
- If one day I change supplier, what is needed for the handover?
- Who has access to my customers' data, and where is it stored?
It applies to off-the-shelf products too
With subscription software the code will never be yours, and that is normal. There the question becomes: can I take my data away in full if I stop using it? It is one of the criteria for choosing between off-the-shelf and custom software.
We are explicit about this from the start: the code, access credentials and documentation of what we build stay with the client.
In sintesi
- Domain and access in your name, always.
- Code and documentation handed over in a reusable form.
- Data exportable in a readable format.
- Ask before you start and have it written into the contract.
Talk to us about your project
Free first assessment, reply within 24 business hours.