No. We start with the services where an outage hurts customers or revenue most; others can keep simpler monitoring.
Riyadh Services
Best Site reliability and production engineering company in Riyadh
Service level objectives, error budgets and incident practice that turn outages into lasting fixes. Hosn Al Tomoh works with organisations in Riyadh on site reliability, agreeing scope, responsibilities and proof of completion for each phase from the start.
Site reliability engineering sets service level objectives for the journeys customers care about, then uses error budgets to balance new releases against stability. Incident command, post-incident reviews and game days turn outages into lasting fixes.
Saudi programmes usually have to account for the Essential Cybersecurity Controls of the National Cybersecurity Authority (NCA), the Personal Data Protection Law overseen by SDAIA and, for government entities, the standards of the Digital Government Authority. Banks answer to SAMA, and insurers to the Insurance Authority. We plan hosting, data classification and evidence around these from the start, and quote in Saudi riyals.
Your teams keep oversight throughout, and before we step back we hand over the runbooks and train the people who will run the work.
The scope can run from a short diagnostic to a phased rollout, and each phase is fixed before it starts.
What the work covers
We measure success in working systems and agreed metrics, not in recommendations.
- Service level objectives for the customer journeys that matter most.
- An incident command process with clear roles and blameless reviews.
- Game days that test failover and runbooks before a real outage does.
What we check first
SRE fails when it becomes a renamed operations team. We start with two or three critical services, agree their objectives with the product owners and make the error budget part of every release decision.
At the end of each phase we provide the proof your risk and audit teams need to file: test results, access reviews and signed handover documents.
Before you start
Practical questions from IT and procurement teams.
Each phase is scoped and priced separately, with the team, the deliverables and the acceptance criteria written down, and you receive an itemised quote before work starts.
Your team, unless you choose managed services. We name who is responsible for each component before launch, hand over the runbooks and train your people.
How the work runs
Four stages, each with clear criteria for moving to the next.
Discover
We document the current set-up, the people involved and the constraints, and agree what success looks like.
Design and plan
We set the target design, phases, test approach and acceptance criteria, and review them with your architects and risk team.
Build and test in stages
We deliver in increments, testing and demonstrating each one before the next begins.
Hand over
We hand over runbooks, train your team and support the launch, then formally transfer responsibility to the people you nominate.
Ready to mature your operations?
Book a technical consultation with our principal engineers to map out your architecture and transition plan.