New name. Twenty years of experience.
The engineers behind AfterHoursOps have managed customers' production operations since 2005 at Server Surgeon. Now we do it for you, during the coverage window you choose, so your team can switch off.
Why we built this.
John Meacham writes:
We started AfterHoursOps because of what we kept seeing at Server Surgeon. For years, customers handled their own production, the day-to-day maintenance and the middle-of-the-night alerts alike, because hiring more staff to cover it was hard to justify, and waking up at 3 a.m. couldn't go on forever.
We've managed production for other people's companies for two decades, across Linux and every major cloud. There isn't much we haven't seen. The name is new. The people behind it are not.
— John Meacham, Founder
Real people you'll get to know.
We're a small team of senior engineers. The engineer working your issue signs their name to every ticket and email, and you'll also have a named primary technical contact for your account. Between us, we have more than 130 years of combined production experience:
- John M. — Founder — 28 years experience
- George Z. — Senior System Administration & Support Manager — 23 years experience
- Alexander P. — Senior System Administrator — 20 years experience
- Edward P. — Senior System Administrator — 17 years experience
- Scott M. — Senior System Administrator — 16 years experience
- Thomas J. — Senior System Administrator — 14 years experience
- Sal I. — Senior System Administrator — 14 years experience
From the team behind Server Surgeon.
Our parent company, Server Surgeon, has managed customers' production servers since 2005, and cloud environments since AWS launched EC2 in 2006, on through Azure, Google Cloud, and the rest. That's 20+ years of production operations experience, the same engineers and the same discipline. You can check the track record yourself.
Visit Server Surgeon →You're trusting us with production. We treat it that way.
Our access to your systems is least-privilege and logged. You set the guardrails and escalation rules, the lines we don't cross, and you can see what we did and when.
How we handle a 3 a.m. incident
An alert fires at : response times on the database server are climbing fast. Within 10 minutes, a named engineer is on it, not an auto-acknowledgement. They check the dashboards, find an overnight backup job saturating the server's disk I/O, and pause it. Response times fall back to normal, and the backup gets rescheduled to a quieter window so it doesn't happen again. The site stays up. In the morning, you get a short write-up of what happened and what we did. You slept through it.
Easy to try, easy to leave.
30-day money-back guarantee · No long-term contract, month-to-month · No setup fee · Backed by a written SLA, with custom SLAs available
Founding customers.
Early customers take a chance on a young company, so our first 10 lock today's price for 5 years, in writing. We call them our founding customers, and we look after them.
Let's talk.
Tell us what you run and the hours you want covered, and we'll send you a quote. No obligation.