Cloud Infrastructure
Servers, databases and networks as source code — traceable and rebuildable at any time.
- AWS
- Hetzner
- Infrastructure as code
How it works
For us infrastructure is a file in the same repository as everything else, not a sequence of clicks in a web console.
Everything described
Servers, databases, networks, certificates: as source code, versioned, reviewable. Whoever changes something changes it visibly. And a second environment is one command rather than an afternoon.
Separate environments
Test and production run separately and look the same. A bug that only appears in production because production is configured differently costs the same baffled day every time.
Backups that have been tested
We set up backups and restore them as an exercise. A backup that has never been restored is a hypothesis — and that becomes apparent at exactly the wrong moment.
Sized to fit
We take what matches your load. For many projects that is two servers with a European provider rather than the full apparatus of a hyperscaler. When you grow, it grows.
- A decision on the provider, if you have requirements. Otherwise we propose one.
- Your server location and the retention periods from the data protection concept.
- An account with the provider in your name. The invoice should arrive at your address.
Infrastructure described in source code, separate environments for test and production, and backups with a tested restore.
If you skip this
Servers set up by hand are known only to the person who set them up. When something fails, it gets reconstructed rather than restored — and nobody can be sure the new state matches the old one.
Questions about this step?
A conversation costs nothing and takes half an hour. Afterwards you will know whether we are a fit.