Senior operations since 2005.
The engineers behind After Hours Ops have managed customers' production operations since 2005 at Server Surgeon. Today we're the night shift behind agencies and AWS partners: the same engineers, handling your clients' incidents under your brand.
Why we work for agencies.
John Meacham writes:
I've managed production for other people's companies for two decades, first servers, then cloud, at Server Surgeon and now here. In all that time, the worst version of the 3 a.m. problem I've seen isn't the company whose own site is down. It's the agency that promised a client "we've got you covered" and has one exhausted lead developer keeping the promise.
That's why After Hours Ops works the way it does. We sell only to agencies and cloud-first partners, and we will never compete with you for your clients: it's written into every partner agreement, and I'll show you the clause before you've signed anything, because nothing else on this site matters if you can't trust that.
My name is on this company. If we ever fall short of what these pages promise, email me directly and I'll make it right.
— John Meacham, Founder
The people you're putting in front of client production.
We're a small team of senior engineers, and every one of them is someone you can stand behind in front of your own client. The company is US-owned and US-led, run from Phoenix, Arizona, with engineers on real, staffed shifts around the world. The engineer on your client's issue signs their name to every ticket you see, and you'll also have a named primary technical contact for your account. Between us, 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. None of it is new to us, and you can check the track record yourself.
Visit Server Surgeon →Deepest on AWS, earned the slow way.
AWS is the only specialization we claim, and we're building our AWS Partner standing the same way we run production: methodically. Our AWS Select Tier partnership is in progress, and we'll update this page as each milestone lands. You won't find a badge here we haven't earned; we'd rather show you two decades of AWS operating history than a logo.
You're trusting us with client production. We treat it that way.
Access is least-privilege and scoped per client environment, every session traces to an individual named engineer, and everything we do lands in the client's own audit records, where we can't alter it. You set the guardrails and escalation rules per client, and any client can revoke our access at any time, without our cooperation.
See how it works →What a covered night actually looks like
A typical covered night, as it plays out for a partner:
An alert lands at : the disk on a client's application server is filling, and at the current write rate it has about two hours left. Within 15 minutes a named engineer has it, not an auto-acknowledgement. That client's guardrails sit beside the alert: reclaiming space is ours to do, changing how the logs rotate is not. They clear the old log archives, confirm the write rate has flattened, and stay with it through the next hour to be certain. The site never went down and the client never wrote a ticket. What the engineer does not do is rewrite the rotation policy at 2 a.m. to stop it recurring, because that is a production config change and it sits on your side of the line. By morning the ticket tells the whole story: what filled the disk, what was cleared, how much room that bought, and the one change we would make next, with the reasoning, ready for you to approve or wave off.
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 · Add or remove client environments as your client base changes
Put names you can trust behind your care plans.
Tell us about your client base, or bring one client environment and we'll draft the client guardrails together. No obligation.