01
We answer for what we run
If something we run goes wrong, it is our problem, including when that is inconvenient or when the mistake was ours. We look for the cause and fix that, and we tell you early rather than late. We also watch what your product costs and how it performs, because a closed ticket tells you neither.
02
We help with more than the contract covers
Sometimes the useful thing is outside our scope: a view on your business, an idea nobody asked for, an introduction to a vendor, or to another customer of ours who has solved the same problem. When it helps both sides, we make the introduction.
03
We do not favour a cloud
No cloud, product or partner programme decides what we recommend. We work with the tools you already have and suggest others when they would help. If a simpler or cheaper option is the right one, we say so, even when it means less work for us.
04
We build what we run
The people who design a platform are the people who operate it, so we only design things we would be willing to be on call for. What we learn in operations goes straight back into how we build, and nothing depends on one person on our side.
05
Everything is code, and much of it is public
Infrastructure and configuration are written as code, and changes are reviewed before they are applied. Our own Terraform modules, Helm charts and tools are on GitHub.
06
We learn before we change
We start with read-only access and an assessment, and we ask why something is the way it is before we replace it. Then we change things in small steps: dev and test first, one piece at a time, each with a way back. We would rather make ten boring changes than one heroic one.
07
Clear language and clear billing
We explain what we are doing as we go, without jargon. Our hours and prices are written down, packages run month by month, and we report on the things that matter to your business.