DevOps Services
A reliability engineer on call, without hiring one
A senior reliability engineer without the full-time hire. Software watches 24/7 and runs known fixes; a real engineer answers within minutes, day or night.
Most teams start with the free AWS bill check. Once the bill is down, we review the rest of your setup for free, and this is one of the things we can take on. How the steps work
Nobody owns the 3 a.m. problem
Your app runs. Your developers build features. Nobody's job is keeping it up. When something breaks at night, it waits until someone wakes up, or until a customer writes in.
Hiring a full-time site reliability engineer costs a senior salary, and most small teams don't have a full-time job's worth of reliability work. So the work goes undone until the night it matters.
SRE stands for site reliability engineering: keeping an app up, fast and recoverable. Fractional means you get a senior engineer for the part of the job you need, not a full-time hire.
What could happen
- An outage nobody sees for hours. A disk fills overnight, the app stops saving orders, and the first person to notice is the first customer in the morning.
- The developer who gets every page. One person carries the phone. Holidays get interrupted, and if that person leaves, the knowledge goes with them.
- The same fire, every month. Without someone writing down what broke and why, the same problem comes back. Each time it costs a morning.
- A launch nobody planned for. A campaign or a press mention sends traffic your setup has never seen, and nobody checked the limits beforehand.
How it works
Software does the watching. A senior engineer does the thinking. The same approach runs our own systems.
- Watched around the clock. Your app is checked from outside every few minutes, plus disk, memory, database and certificate dates. Alerts come to us first.
- Known problems get the known fix. Each common problem has a written runbook: restart a stuck service, clear a full disk, roll back the last release. Software runs those steps the same way every time, and every action is logged.
- A real engineer, at any hour. Anything outside a runbook goes to a senior engineer. In practice that is usually within minutes, day or night. The response time we guarantee for urgent issues is written into your agreement before you start.
- You hear it in plain words. What broke, what we did, whether anything is still at risk. No dashboard to decode.
- The fix stays fixed. After every incident we write down the cause and change what let it happen, so the next alert is less likely.
- Ahead of the slow problems. Capacity, database growth, expiring certificates, and checks before a launch, so fewer things break at night.
What you can do yourself today
- Decide who gets the alert at 3 a.m. today. If the answer is "nobody" or "a customer," start there.
- Set up a free outside uptime check on your homepage and your login page, with alerts to a phone, not just an email inbox.
- Write down the three things that broke most recently and what fixed them. That list is your first runbook.
- Check how full your main disk and database are, and how fast they grew last month.
What's included in which plan
| Guard $700/mo | Watch $1,200/mo | Operate $2,800/mo | |
|---|---|---|---|
| Checks around the clock, alerts to us first | No | Yes | Yes |
| Runbook fixes for known problems | No | No | Yes |
| A senior engineer on incidents at any hour | No | No | Yes |
| Plain-words incident notes and the fix that stops it repeating | No | No | Yes |
| Capacity watch and launch checks | No | Yes | Yes |
| One engineer who knows your setup | No | No | Yes |
Operate setup is quoted after the free review, because it depends on how your app runs today. Month to month, no exit fee. See all plans.
Questions about fractional SRE
Is a person really there at night?
Yes. Software handles the problems it has a written fix for, and anything else goes to a senior engineer at any hour. The guaranteed response time for urgent issues is in your agreement, so you can hold us to it.
What does the AI do, and what doesn't it do?
It watches, sorts alerts, and runs fixes that a senior engineer wrote and tested beforehand. It does not make new changes to your systems on its own. Anything new goes to a person, and every action is logged where you can see it.
Do we still need our own on-call rotation?
Not for the hosting side. Your developers can sleep. If a problem is inside your product's code, we stop the damage first, for example by rolling back the last release, and hand your team a clear note in the morning.
How is this different from a monitoring tool?
A tool sends an alert. Someone still has to wake up, work out what it means and fix it. Here, the alert comes to us, and so does the fix.
How we work with your systems
You stay in control
Read-only access first
The free bill check needs read access and nothing else. Nothing in your systems changes.
You approve every change
Each change comes as a short written note first: what, why, and how to undo it.
Your data and billing stay yours
Everything stays in your own account. We never become your billing contact.
Every action logged
Every action we take is logged, and the log is visible to you.
One-click access removal
Delete the access role and our access ends at once, with no penalty.
Month to month
There is no minimum term and no exit fee. Stop at the end of any month.
Your free AWS bill check, in 48 hours
One read-only template. Every dollar you could stop paying, ranked. You keep the report even if you never hire us.
read-only accessno savings, no feemonth to month
