Valfort Tech
Book a call
SRE consulting so you find outages first
Site reliability engineering (SRE) consulting is outside help to make a production system measurably reliable. Valfort Tech defines SLOs and error budgets for the journeys your customers depend on, instruments services with OpenTelemetry, cuts alerts down to the ones that need a human, and sets up an incident process with blameless postmortems.
When teams call us about SRE
Customers spot outages before you do.
- Customers spot outages before your monitoring does.
- On-call engineers get paged at night for problems that could wait until morning.
- Nobody can state how reliable the product is in one number.
- Incidents end with a fix but no written postmortem or follow-up actions.
- Dashboards exist, but nobody trusts them during an incident.
What we deliver
Everything ships as code in your repositories, with runbooks and a recorded handover.
SLOs and error budgets
Service level objectives for your most important user journeys, with error budgets that tell the team when to ship and when to fix.
OpenTelemetry dashboards
Services instrumented with OpenTelemetry for metrics, logs and traces, and Grafana dashboards built around your SLOs.
Alert cleanup and paging policy
Burn-rate alerts on SLOs replace noisy threshold alerts. Only problems that hurt customers page a human.
Incident process
Clear severity levels, roles, communication templates and an escalation path, written down and rehearsed with your team.
Postmortems
A blameless postmortem template and review habit, with follow-up actions tracked to completion.
Runbooks and handover
A runbook for every paging alert, plus written docs and a recorded handover so your team runs it without us.
Typical results
Pages typically fall 50–80% once threshold alerts are replaced with SLO-based alerts.
SLO burn-rate alerts typically catch customer-facing problems before support tickets arrive.
With clear roles and runbooks, incidents typically resolve faster and with fewer people pulled in.
Typical ranges, not promises. We measure your own baseline in the first week.
How a SRE engagement runs
The first two weeks run on read-only access. Every change after that goes through your pull requests, with one named engineer and a written update every Friday.
- Week 1
- Read-only reviewWe review your monitoring, alert history, incident records and on-call setup on read-only access.
- Week 2
- Roadmap and first fixYou get a scored report and a ranked 90-day roadmap, and we ship one fix to production through your pull requests.
- Weeks 3–8
- SLOs and telemetryWe define SLOs with your team, instrument services with OpenTelemetry and replace noisy alerts with burn-rate alerts.
- Weeks 9–12
- Incident process and handoverWe set up the incident process and postmortems, write runbooks, then hand over with a recorded walkthrough.
Tools we work in
We work in the tools you already run, and only add new ones when they earn their place.
- OpenTelemetry
- Prometheus
- Grafana
- Loki
- Tempo
- Alertmanager
- PagerDuty
- Kubernetes
- Terraform
SRE questions
What is the difference between SRE and DevOps?
DevOps focuses on how software gets built and shipped, while SRE focuses on how it behaves in production. DevOps work covers CI/CD, infrastructure as code and deployments. SRE work covers SLOs, error budgets, alerting, incident response and postmortems. Most teams need both, and Valfort Tech delivers each as code in your repositories.
How much does SRE consulting cost?
Engagements start with a 10-day readiness sprint at a fixed $3,500. You get a scored report, a ranked 90-day roadmap and one fix shipped to production. If we do not find at least three times the fee in savings or avoided risk, the sprint is free. Follow-on work is scoped after the sprint, and the sprint fee is credited to it.
How long does it take to set up SLOs?
A first SLO for your most important user journey can be the one fix shipped during the 10-day readiness sprint. Covering the rest of your services is planned in the 90-day roadmap, and the pace depends on how many services you run and how well they are instrumented today. Each step has an estimate before work starts.
Do we need a full-time SRE team?
Not necessarily. Many teams with 10 to 200 engineers get most of the benefit from SLOs, clean alerts and a clear incident process run by their existing engineers. We set those up as code, write the runbooks and train your team, so reliability becomes part of normal engineering work rather than a separate department.
Which observability tools do you work with?
We build on OpenTelemetry so your telemetry is not tied to one vendor. For storage and dashboards we often use Prometheus, Grafana, Loki and Tempo, and we work with your existing vendor where it already serves you well. Alerts route to the paging tool you use today, such as PagerDuty.
Not sure where to start?
Book a 30-minute call. We'll tell you whether the readiness sprint, a single service or nothing at all is the right next step.