What “code ownership” really means (and why nobody tells you)

Technical dependency is the silent business model of part of the market: as long as leaving is painful, the client stays — not out of satisfaction, but as a hostage.

What you must own

The domain name (in your name, not theirs). The hosting (your account, your invoice). The source code (an accessible repository, not a promised archive). The data (a complete export, in a reusable format). The access (all of it, documented).

The five questions to ask before signing

1. Will the code repository be in my name from day one? 2. What happens if I want to change providers in two years? 3. Is there a reversibility document? 4. Who holds the domain and the hosting? 5. Is documentation a contractual deliverable?

A serious provider answers all five without hesitating. With us, the answer is called the exit kit: it is handed over on delivery day, whether you stay or not. Leaving must be easy — that is exactly why clients stay.