Logistics and delivery / SRE / on-call engineer / Day in the life
Dispatch runs at 4 a.m. So does the pager.
A week of on-call for a 24/7 delivery network, with and without.
Published September 3, 2026/01 / 06
A delivery network has no off-hours: drivers scan at 04:00, warehouses cycle at 02:00, and the pager honors all of it. The 3 a.m. page for a disk at 85% is the emblem: real enough to check, routine enough to resent.
This story follows one SRE through the same week twice. Without: five night pages, four of them routine, each costing a sleep cycle and a next-day. With: agents investigate first, handle what is within policy, and the disk at 85% becomes a line in the morning summary with the expansion already drafted.
Amela’s published AWS result anchors the after: investigation and remediation in under 30 minutes, around the clock. The pager still exists. It just fires for things worth waking for.
#AISRE #Logistics #Oncall #CloudThinker
02 / 06 The problem
One SRE’s week on a 24/7 network, without
Mon 03:12
Disk at 85%
Real threshold, routine cause. Twenty minutes to confirm, expand, and fail to fall back asleep.
Tue 02:40
Queue depth alert
Warehouse batch job overlapping with backups, again. Known issue, unowned.
Wed 04:05
Scanner API timeout
Self-resolved before the laptop opened. The sleep is still lost.
Thu
The daytime cost
Code review skipped, project work slips. Tired engineers make tomorrow’s incidents.
Fri 03:30
The real one
Routing service degradation. Handled well, by an engineer running on four hours of sleep.
Sunday
Handover
A Slack thread of five nights, read by nobody, and the next rota inherits nothing.
Four of five pages needed a decision-maker for zero of the decisions.
03 / 06 Why the current answers fail
Two ways to fail: keep doing it by hand, or hand production to an agent on day one
Option A: the status quo
One-off scripts
one per account, none the same
Tribal knowledge
the standard lives in someone’s head
Manual follow-up
tickets chased, dashboards watched
Quarterly evidence
compliant in audit week, unknown after
Resultsafe, does not scale
Option B: AI with full access
Trust on a promise
a demo is not a control
Unscoped credentials
one key for cloud and on-prem alike
Recommendations only
still a human acts, still no evidence
No audit trail
the regulator asks; the chat log answers
Resultscales, nobody signs off
What the 24/7 ops teams we work with chose
Neither. Agents take first response all night, act within the policies the team set, and wake a human only when the decision is genuinely human-sized.
Trust is not granted to a system. It is earned, one audited check at a time.
04 / 06 Frontier Investigation Agents
Four steps from read-only to autonomous. The team decides when to take each one.
Step 1
VerifyRead only
Live inventory, drift, waste and health checks. Nothing changes. Every finding explains what was checked, what was found, why it matters.
Step 2
EncodeStandards as Skills
Naming, tagging, guardrails, cost controls and runbooks written once and run the same way in every account. Tribal knowledge becomes a file.
Step 3
The gateAct with approval
Agents investigate and propose. A person approves where risk, policy or production impact demands it. Every action is written to the audit trail.
Step 4
Auto modeAutonomous under guardrails
Per environment, the team sets Notify, Act-with-Approval or Autonomous. Low-risk remediations run on their own. Production keeps the gate.
The SRE’s question
“Which of those five nights would it have taken?”
Four, under a normal policy: disk expansion, the known batch overlap, the self-healing timeout, and triage on the queue alert. The routing degradation still pages you, with the investigation already attached.
Frontier Investigation Agents for your cloud. They scale the team’s judgment, they do not replace it.
05 / 06 Proof
The same week, with
Mon to Thu
Zero night pages
Routine events handled within policy, each one logged with its evidence.
Fri 03:30
One page, pre-investigated
The routing incident arrives with a correlated cause and a drafted fix. One approval.
Every morning
The summary
What happened overnight, what was done, what needs a human decision today.
Hours per incident
<30 min
from alert to investigated root cause and applied remediation on AWS.
On-call became a role again, instead of a tax on sleep.
06 / 06 One number, and the ask
The only number we ask you to check yourself
Read-only, first 30 days
Zero changes to production
Start the way our customers did. One scoped, read-only key. The engine inventories your estate and reports drift, waste and health. Your team checks the findings against what it already knows. If they hold, you decide the next step.
What you get
1 report
Full inventory, drift and waste findings, each with what was checked and why it matters.
What you risk
1 read key
Scoped and revocable. Every check it runs is in the audit log from day one.
Do not trust the AI. Verify it. Then let it earn the next step.
Sources
- Amela (AWS at scale): Incident investigation and remediation from hours to under 30 minutes. Borrowed from the closest public evidence for this vertical.
- Proof anchor, borrowed from the closest public AWS-scale evidence: Amela
The evidence
Amela
Incident investigation and remediation from hours to under 30 minutes.
Read the full evidenceThe module
OnCall
The part of CloudThinker this story runs on, in product terms.
Explore OnCall