You get the source code. All of it.
A permanent right to use it, change it, and have anyone maintain it. No expiry, no renewal, nothing we can revoke.
Stop paying us and nothing stops working.
Here’s what gets handed over.
The source code. Every line, in a repository you control.
The tests. The automated checks that prove it works, so anyone can verify it still does after they change something.
The documentation. How it’s built, how it’s structured, why the decisions were made the way they were.
The deployment pipeline. The mechanism that puts new versions into service.
The dependency list. Everything it relies on and which version, so nothing is a mystery later.
Why it’s fast.
Every build makes the next one faster. We reuse the components and patterns we’ve developed — the scheduling logic, the infrastructure, the standards. That’s why this costs a fraction of what starting from a blank page costs.
What we never reuse is what makes your business yours. Your workflows, your process, the parts that are the reason you’re different. Those stay yours.
And if you want it fully exclusive — nothing reused, ever — that’s available. It costs more, and most people find they don’t need it.
Who maintains it is your decision.
Your own team, if you have technical staff. It’s built to standards a developer will recognize, and documented for exactly this.
Any developer you hire. You’re not required to come back to us. The documentation exists so someone who has never met us can pick it up.
Us, on a maintenance agreement. Same system that built it handles changes and additions.
You can start with one and move to another.
And where it runs is a separate decision.
On your infrastructure. Your servers, your cloud account, your control. We hand over the deployment pipeline and it’s yours to run.
On ours. We host it, keep it running, handle updates and backups, and maintain it. A monthly cost, no infrastructure for you to manage.
Hosting includes maintenance — if it’s running on our infrastructure, we’re responsible for it being up, which means we’re the ones changing the code.
If you’re hosted with us and later want to bring it in-house, you take the code and the pipeline and go. That option never closes.
The thing people are actually worried about.
Custom software has a reputation. Built, delivered, then slowly abandoned — until it breaks and nobody knows how to fix it.
That reputation is earned. It happened because software was hand-built by specific people, and when those people left, the knowledge left with them. What remained was code nobody could safely touch.
That’s the part that changed. It wasn’t hand-built, so the knowledge isn’t in anyone’s head. It’s in the documentation, the tests, and the structure — which is what makes it possible for someone else to take over.
And if you walk away, you keep everything.
No account to cancel. No data to export. No period where it still works while you find a replacement.
It was working software the day it shipped, and it stays that way.