What you own
Everything we build for you: source code, infrastructure definitions, designs, automated tests, documentation and the written spec. Once paid for in full, it is yours to run, change, sell or hand to another supplier.
When ownership passes
Ownership of the work passes to you when you have paid for it in full. The terms say the same: full ownership of deliverables transfers to the client upon receipt of full payment. The assignment is written into your agreement, not implied by this page.
The written spec follows the same rule: once you have paid for it, it is yours to keep and use as you choose.
Open-source components keep their own licences. We list them, with their licences, in the handover pack.
Your repository, your cloud, your domains
From the first day, the work lives in accounts you own:
- Repository. We create it in your organisation, with you as owner. Every commit, from the first one, is in your history.
- Cloud. Environments run in your AWS, Google Cloud, Azure or Cloudflare account. You are the account owner and you pay the provider directly.
- Domains and DNS. Registered in your name, at a registrar you control.
- Secrets. Stored in a secrets manager inside your accounts.
Our access is a scoped role that you grant and can revoke at any time. At handover we remove it on request.
Warranty
After handover, a defined warranty period covers defects in what we delivered. The period is stated in days in your agreement and starts on a date written there. Each defect is given a severity level. For each level the agreement sets two figures: how quickly we respond, and how quickly we fix.
Warranty covers defects. It does not cover new features, changes to third-party services, or changes made to the code by someone else without our review. You are not billed for warranty fixes.
Support after the warranty is optional and separate. Taking it or not has no effect on who owns the work.
Exit and handover
Because the repository and the cloud accounts are already yours, leaving does not depend on us. Your code, your deployments and your domains stay exactly where they are, and the system keeps running.
You can ask for handover at any time. Notice and payment for work already done are set in your service agreement. What we hand over:
- The repository, with its full history, under your ownership.
- Documentation: architecture, how to run and deploy it, and a runbook for common faults.
- The automated test suite and the pipeline definitions that run it.
- Infrastructure definitions for everything we built.
- A list of every third-party service, account and licence the system depends on.
- Credentials rotated, with a record of what changed.
- A training session for the people who will run it next.
- Removal of our access to your accounts.
No lock-in
Nothing about how we build ties you to us. The stack is standard and named in the documentation. There is no proprietary framework and no hosting that only we can reach. A new supplier can pick the work up from the handover pack.
What we won’t do:
- Hold your code.
- Run your system in an account you do not own.
- Make an exit depend on our cooperation.
- Charge you to hand over what is already yours.
Where the full terms are
This page summarises the commitments. The binding wording is in your service agreement and in our terms. How your data is handled is on the security and privacy page. What the first paid step produces is on the spec page.