Releases that are routine and infrastructure you can rebuild. We set up the code, pipelines and platforms that make both true.
Where we start
- Infrastructure defined in code
- Pipelines from commit to production
- Kubernetes run properly
- A platform developers serve themselves from
Works with
Kubernetes
Terraform
Docker
GitHub
GitLab
Ansible
Grafana
Amazon Web Services
Practices / 02
Five practices,
one platform.
- 01
Infrastructure as code
Servers, networks and DNS written in Terraform or Pulumi and reviewed like code, with drift detected and secrets kept in a vault.
- 02
Delivery pipelines
Tests, security scans and approvals on every change, with gradual releases and a tested rollback.
- 03
Containers and Kubernetes
Hardened clusters with autoscaling, access control and storage for the workloads that need it.
- 04
Platform engineering
Templates and golden paths, so a new service starts with pipelines, monitoring and security in place.
- 05
Reliability
Service level objectives, alerts on what users feel, and a written review after every incident.
Process / 03
Assess,
then automate.
- STEP-1
Assess
Your toolchain, releases and incidents, and where time is lost.
- STEP-2
Plan
A sequenced roadmap that starts where the gain is largest.
- STEP-3
Build
Code, pipelines and platform delivered in increments, in your own accounts.
- STEP-4
Hand over or run
Runbooks and training for your team, or we operate it for you.
How we run our own
Our own estate is defined in code and deployed from git: a live change made by hand is reverted automatically. It is the setup we recommend.
Make releases boring.
Tell us how you ship today. We will say what we would change first.
Managed IT and cloud