How a change reaches production
Every change follows the same path, so releases can happen on a weekday afternoon without a meeting first.
- You have
Your code
A change to the application or the infrastructure.
- Step 1
Build and test
Built and tested automatically on every change.
- Step 2
Staged release
Staging first, then a gradual rollout to production.
- Step 3
Monitoring
Alerts on problems customers would notice, each with instructions.
DevOps services
We set up the pipeline, environments and monitoring, and hand them over with instructions your team can follow.
Releasing
- Automated releasesEvery change built, tested and deployed through a pipeline.
- Gradual rolloutsNew versions reach a small share of users first.
- ContainersApplications packaged as containers and run on Fargate, Cloud Run or Kubernetes.
- Moving to containersServices moved from virtual machines one at a time, old and new side by side.
Running
- Infrastructure as codeEverything defined in Terraform and reviewed before it changes.
- MonitoringLogs, metrics and traces in one place, with alerts that have written instructions.
- Cloud costSpend tracked by service and environment, with a monthly review.
- On-callAlert response on a support agreement, or a setup your own team can run.
Tools we work with
If your team’s current tools are working, we keep them.
Build and release
- GitHub Actions
- Azure DevOps
- Docker
- Helm
- Kubernetes
Infrastructure and monitoring
- Terraform
- CDK
- Prometheus
- Grafana
- CloudWatch
Questions we get on the first call
Have a question that is not here? Send it with the form below and an engineer will reply within one business day.
Can you move an existing application to containers?
Yes, one service at a time, running old and new side by side until they match. We will also tell you if Kubernetes is more than you need and suggest Fargate or Cloud Run instead.
Which tools do you use?
Terraform, Docker, Helm, GitHub Actions and Prometheus with Grafana by default, plus your cloud provider’s own services where they do the job. If your team’s current tools are working, we keep them.
Do you take on-call?
Yes, on a support agreement with agreed hours and response times. Or we set up the rota, alerts and instructions for your own team.
Four ways to work with us
A defined project
A defined integration or product, priced and scheduled up front, delivered with the test suite and infrastructure code you keep.
Engineers on your team
Engineers who join your team, your code and your daily meetings for as long as the roadmap needs them.
Ongoing support
We keep the integrations you run working: monitoring, vendor updates, new connections and month-end support.
Taking over existing systems
A system or integration nobody wants to touch: we review it, make it stable, then build on it.
