Do you own the software we build for you?

Yours from the first commit

Your code lives in your repositories, under your organisation, from day one. We work inside it; we do not hold it hostage in an account you cannot reach. There is no separate licence to buy back and no escrow clause that releases your own software to you only if you behave. You paid for it, so it is yours, continuously.

What 'yours' actually covers

The application code and its history, the infrastructure definitions, the deployment configuration, the documentation, and the credentials to the services it depends on. We bill the infrastructure it runs on separately and in your name, so the hosting relationship is yours too. Nothing about the way we work requires us to stay for the software to keep running.

Why we are comfortable saying it

Our promise is 'Your software. Our responsibility.' We earn the next month by being the best people to maintain and move the software forward, not by making you dependent on us. A partner who has to trap you is telling you something about the work. We would rather you could leave and choose not to.

Straight answers.

Do you keep a copy or any rights to the code?

No rights. We keep access only for as long as we are working for you, and only to the repositories and services the engagement covers. The intellectual property is assigned to you, not licensed.

What happens to the software if we stop working together?

You keep a running system and everything needed to operate it or hand it to another team: the code, the infrastructure, the documentation and the accounts. We help with a clean handover.

Is the hosting in your name or ours?

Yours. Infrastructure is billed separately and set up under your account, so you are never locked out of the environment your own software runs on.

Keep reading.

Your software. Our responsibility.