OppexOppex

Manage Incidents Effortlessly,Without the Noise.

Being On-call should not cause you stress. Focus on the right incidents. Be prepared for incidents more than ever with Oppex Incident Management stack

oppex.app — Scheduling
CapillaryCommerceIQFacetsHectorSessionM
Signal over noise

Reduce noise and alert fatigue

Cut through repetitive alerts and surface what actually needs attention, so on-call responders spend less time sorting through noise and more time resolving what matters.

cpu high
5xx spike
lb timeout
cpu high
retry burst
p99 ↑
disk 91%
5xx spike
edge 502
queue lag
cpu high
retry burst
p99 ↑
edge 502
mem 88%
5xx spike
lb timeout
queue lag
cpu high
edge 502
cpu high
5xx spike
lb timeout
cpu high
retry burst
p99 ↑
disk 91%
5xx spike
edge 502
queue lag
cpu high
retry burst
p99 ↑
edge 502
mem 88%
5xx spike
lb timeout
queue lag
cpu high
edge 502
20 ALERTS──▸1 INCIDENT
CORRELATED · INC-2506
SEV-2
Edge routing degradation in eu-west-1
Grouped from 20 alerts across 4 services · 1 responder paged
On-call readiness

Go on-call with confidence

Give every responder the context they need before their shift begins - from active incidents and recent changes to what happened during the previous rotation.

JL
Jonas L.
SHIFT ENDING
PR
Priya R.
ON CALL · 09:00
ACTIVE INCIDENTS
INC-2506 · Edge routingInvestigating
RECENT CHANGES
7 deploys in the last 24hbilling, edge
HANDOFF NOTE
Watch billing retries — spiked twice overnight, mitigation is temporary.
Flexible scheduling

Create schedules that are as flexible as your team requirements

Build rotations around the way your team actually works. Create layers, define rotations, manage overrides and adapt coverage without rebuilding your entire schedule.

payments-primary
4 LAYERS · WEEKLY
MONTUEWEDTHUFRISATSUN
FINAL
Priya
Jonas
Sam
Mei
LAYER 1
Priya
LAYER 2
Jonas
LAYER 3
Weekend · Sam
LAYER 4
Mei
168H COVERED · NO GAPS1 OVERRIDE THIS WEEK
Terminal-first response

View, update and resolve incidents from within your terminal

Connect Claude or Codex with Oppex to inspect incidents, get context and take action without leaving your development workflow.

zsh · oppex-mcpMCP CONNECTED
$ oppex incidents --mine
INC-2506 · edge-routing · SEV-2 · triggered 4m
$ what changed before it fired?
3 deploys · cfg change to edge-lb · 02:41 UTC
$ ack and assign to me
✓ acknowledged · owner: you
$ oppex resolve INC-2506
✓ resolved · 6m · runbook updated
$ oppex incidents --mine
INC-2506 · edge-routing · SEV-2 · triggered 4m
$ what changed before it fired?
3 deploys · cfg change to edge-lb · 02:41 UTC
$ ack and assign to me
✓ acknowledged · owner: you
$ oppex resolve INC-2506
✓ resolved · 6m · runbook updated
TRIGGERED→RESOLVED · 6m▍
Know what's happening

Be on top of what's going on

Ask questions about your on-call operations and instantly understand incident patterns, responder workload and performance without digging through reports manually.

What happened during last week's on-call?
14 incidents, down 22% week over week. Billing accounted for a third of the pages.
MTTA
2m 40s
MTTR
31m
PAGES
14
PAGES BY DAY
M
T
W
T
F
S
S
On-call anywhere

Track incidents on the move

Stay connected to active incidents wherever you are. See what needs attention, follow progress and take critical response actions directly from the Oppex mobile app.

09:14▮▮▮
Incidents
ON CALL
INC-2506 · SEV-2NEW
Edge routing degradation
INC-2501 · SEV-3ACKED
Billing retries elevated
INC-2496RESOLVED
Notifications backlog
LIVE ACTIVITY
Priya acknowledged INC-2506
Error rate falling · 4.1% → 0.6%
Acknowledge
···

What makes on-call sustainable.

Eight strengths that keep coverage reliable without burning out the people carrying the pager.

Flexible scheduling

Build rotations, layers and overrides that match how your team actually works - not the other way around.

Layered coverage

Stack primary, secondary and specialist layers so every service always has someone who owns it.

Smart escalations

Unacknowledged pages move automatically through the escalation chain until a real responder takes ownership.

Minimal alert fatigue

Correlated, deduplicated alerts mean the pager only rings for what actually needs a human.

Timezone aware rotations

Coverage follows the sun across regions, so no one is paged at 3am for someone else's business hours.

Instant overrides & always-on coverage

Swap a shift or cover a gap in seconds, with zero blind spots in the schedule while you do it.

Full mobile control

Acknowledge, escalate and resolve incidents from the Oppex mobile app without waiting to get back to a desk.

Fair rotation history

See exactly who was on call and when, so coverage stays balanced and no one carries an unfair share of the pager.

Never wonder who's on call again.

See how Oppex builds fair rotations, escalates automatically, and keeps your team reachable around the clock.