You should own 100% of the software you pay to build.

Why vendor lock-in happens

Lock-in is rarely an accident. For a lot of agencies it is the business model. If the only copy of your code lives in the vendor's account, or the application only runs on the vendor's proprietary runtime, or the contract grants them the IP and licenses it back to you, then leaving is expensive by design. Renewals, change requests, and "maintenance retainers" stop being a choice and become a tax. The software you paid for becomes leverage held over you.

It shows up in subtle forms too: undocumented systems only the original team can change, secrets and infrastructure configured in accounts you cannot see, or a no-code/low-code platform that traps your logic in a format you cannot export. The common denominator is that you cannot walk away with the thing you paid to create.

The cost is rarely visible up front. It surfaces a year or two later, when a roadmap change, an acquisition, or a simple disagreement over price means you need to move — and you discover the price of leaving was quietly baked into the original deal. By then the leverage has shifted entirely to the vendor, and the only options are to keep paying or to rebuild from scratch.

What real ownership looks like

Genuine ownership is concrete and verifiable. You should be able to point at each of these and confirm it is true:

• Your repository, from commit one. The code is committed to your own GitHub (or equivalent) organization from the start — not transferred at the end, if you remember to ask.
• Full intellectual property. You hold the IP outright. There is no clause licensing the work back to you and no "shared" ownership.
• No proprietary runtime. The software runs on standard, portable infrastructure you control. There is no black-box platform you must keep renting to keep the lights on.
• Complete handover. Documentation, architecture notes, environment configuration, and deployment instructions come with the code, so any competent team can pick it up.
• No license-back, no hostage. You can move to another vendor, hire in-house, or keep working with us — entirely your call, with nothing technically or legally stopping you.

Doesn't that make it easy to leave?

Yes — and that is the point. A studio that can only keep clients by holding their software hostage is telling you something about the quality of its work. We would rather earn the next phase by being good than by being the only ones with the keys. When the relationship continues, it should be because we are the fastest, clearest, and most reliable option for what comes next, not because leaving is painful.

This is also why our delivery model and our ownership stance fit together. Because Kinisys is AI-only — agents build, senior engineers architect and review — the cost of producing and maintaining software is structurally lower, so we do not need lock-in to make the economics work. And because every line is reviewed by a senior and documented, the codebase we hand over is one another team can actually read and run.

The principle, stated plainly

If you pay to build software, you should own all of it — the code, the IP, and the ability to walk away. Ownership is not a perk we add on; it is the default we start from. The repository is yours from the first commit, the handover is complete, and the only reason to keep working with us is that you want to.