Developers and engineers
You are handing a system to us, or taking one from us, or extending one together. Either way, you need the work to be readable by the next person.
Last reviewed 17 November 2026.
What you need from an engineering partner
Readable work from us.
Architecture, operations and export documentation.
Where to check: How we work
A respectful takeover of your work.
We read before we change; a written assessment first; we tell you plainly if a rebuild costs less than a rescue.
Where to check: What we engineer
Agreed interfaces.
The interface between your product and the backend, written down and tested.
Where to check: What we engineer
Clear code ownership.
Ownership of what we build is set out in your agreement. Ask for the current agreement through the contact form.
Where to check: Engagement models
What you receive
- Documentation that matches the code
- Tests that run
- Reproducible builds
Questions you will want answered
What stack do you use?
Chosen per system in Discovery and written into the architecture document; our own systems run on AWS.
Will we have access to the repository during the build?
Where we work in your repository, yes: with the access you grant, which you can withdraw.
How are secrets handled?
Managed secrets store in your accounts, never in code.
Tell us what has to work.
A scoping call, then a written quote or a Discovery proposal.