Everything in code
Terraform or equivalent, in your repository, reviewable. No console-only resources, no snowflake environments.
Service 05
Cloud and DevOps you can hand back
Infrastructure as code, SLOs that mean something, a real on-call rotation, and a quarterly review of what it all costs.
Softrear builds and operates cloud infrastructure as code on AWS, GCP and Azure, with CI/CD, observability, defined SLOs and an on-call rotation — set up so your own team can take it over without a knowledge transfer crisis.
Who this is for
- Your infrastructure was clicked together in a console and nobody remembers by whom.
- Your cloud bill grows every quarter and nobody can explain which service did it.
- You have monitoring dashboards nobody looks at and alerts everybody mutes.
What you get
Deliverables, not adjectives.
Pipelines that gate on evidence
Tests, security scan, performance budget and a reproducible artifact. If the pipeline is green the change is safe, or the pipeline is wrong and we fix the pipeline.
Observability that answers "is it broken?"
Traces, structured logs and metrics tied to SLOs the business recognises — not 400 dashboards.
On-call that is humane
Runbooks, alert budgets, and alerts that only fire when a human must act. An alert nobody acts on is noise that hides the real one.
Cost review every quarter
What you spend, on what, and what we would turn off. We have cut bills by a third without touching a feature.
How it runs
- Inventory what exists, including the parts nobody documented
- Codify it, environment by environment, without a big-bang migration
- Add SLOs and alerting tied to them
- Run it with you, then hand the pager over when you want it
Tools & standards
We choose per project and write down why. A stack chosen because it is what the last team knew is a stack nobody can defend at review.
Questions we get asked
Do you lock us in?
No. The infrastructure code, the runbooks and the dashboards are in your repository under your licence from the first commit. The handover plan is written at the start of the engagement, not at the end.
Kubernetes or something simpler?
Usually something simpler. Kubernetes is worth its operational cost above a certain scale and team size, and below that it is a tax. We will tell you which side of the line you are on.
The rest of the stack
01
Product design
Research, flows, a design system your engineers can actually build against — not a Figma file that dies at handover.
02Mobile
Flutter, React Native and native iOS/Android — shipped through the stores, instrumented, and supported after release.
03Backend & APIs
Domain modelling, event architecture, contract-tested APIs, and the unglamorous migration off the system you cannot turn off.
04Web frontend
Marketing sites, dashboards and customer portals built for Core Web Vitals, accessibility and the person maintaining it next year.
06Managed support
SLA-backed support for systems we built and systems we inherited, with the metrics published to you monthly.
Tell us what’s stuck.
A senior engineer reads every one of these. If we’re not the right fit we’ll say so, and point you at someone who is.
Start the conversation
No spam, no drip sequence. A senior engineer replies within one business day.