Engineering operations is the layer where the team runs itself — how incidents are handled, how on-call works, how services are governed, how decisions get recorded, how coordination happens across shifts. In 2026 the category has expanded enough that no team needs every tool below, but most teams need at least four of them. The list is ordered by how foundational each one is.
PagerDuty or incident.io
Best for: on-call and incident response. Pricing: $19 to $59 per user per month.
Both tools handle on-call rotations, escalation, incident response, and post-incident review. incident.io leans more modern and integrates more tightly with Slack; PagerDuty is more mature and integrates more broadly with everything else.
Where it falls short: Narrow to incident response. Outside on-call, neither solves general coordination.
Linear
Best for: the work tracker. Pricing: $8 to $14 per user per month.
Linear is the engineering operations foundation. Issues, projects, cycles, and roadmap views are all engineers will actually keep current, which makes everything downstream — planning, status, retrospectives — more accurate.
Where it falls short: Not an operations tool by itself. The operations layer is what you build on top of Linear.
StandIn
Best for: shift continuity and decision governance. Pricing: subscription tier per org.
StandIn handles the operational layer that no other category covers: handoffs across shifts, declared state for queryable status, decision logging with authority, and Representatives that answer with sources. For distributed engineering operations, this is the layer that breaks first without dedicated tooling.
Where it falls short: Not an incident response tool. PagerDuty and incident.io stay in their lanes.
Governance, not a status channel
StandIn is async governance infrastructure. Engineers declare working state before they go offline. Representatives answer from the record, cite the source, and refuse when the answer is not there.
Request access →Cortex or Backstage
Best for: service catalog and developer portal. Pricing: free (Backstage) to enterprise (Cortex).
Service catalog tooling answers the operational question of what exists, who owns it, and what maturity level it is at. For teams with more than fifty services, this becomes essential. For smaller teams, the README pattern still works.
Where it falls short: Heavy implementation. Cortex and Backstage both require real platform engineering investment.
Datadog or New Relic
Best for: observability. Pricing: starts at $15 per host per month.
Observability is the operational foundation for production reliability. Datadog is the broader product; New Relic is similarly capable. Either one done well is worth more than every productivity tool combined.
Where it falls short: Expensive at scale. Cardinality decisions matter more than which tool you pick.
GitHub or GitLab
Best for: the source of truth. Pricing: free to $21 per user per month.
Code, CI, deployment, and code-adjacent documentation all live here. For engineering operations, anything that lives next to the code is more durable than anything that does not.
Where it falls short: Not a coordination tool. The discussion features are useful but not designed for shift-to-shift handoff.
Notion or Confluence
Best for: long-form operational docs. Pricing: $5.75 to $18 per user per month.
Runbooks, postmortems, architectural overviews, and the slow-moving operational documentation live here. Both tools are competent at this; the discipline is what determines the value.
Where it falls short: Documentation drifts. Operational docs that nobody updates become operational hazards.
How to choose
The engineering operations stack should be picked layer by layer. On-call and incident response is one layer (PagerDuty or incident.io). Work tracking is another (Linear). Code and CI is a third (GitHub or GitLab). Observability is a fourth (Datadog or New Relic). Service catalog is a fifth, optional for smaller teams (Backstage or Cortex). Long-form docs is a sixth (Notion or Confluence). Coordination and continuity is a seventh, which most teams underinvest in until handoffs break (StandIn or an assembled equivalent). Skipping a layer to save money is usually false economy; the cost of the gap shows up somewhere else and is harder to measure.
Frequently asked questions
What is engineering operations?
The layer where the team runs itself — incident response, on-call, planning, coordination, decision tracking, and the operational documentation that holds it together. It is distinct from engineering management (which is people) and engineering delivery (which is shipping).
Which engineering operations tools are essential?
On-call and incident response, work tracking, code hosting, and observability are non-negotiable for any team running production services. Coordination and continuity tooling becomes essential once the team distributes across time zones. The other layers (service catalog, long-form docs) scale with team size.
Can one tool cover all of engineering operations?
No, and the products that claim to are usually weakest in their broadest claims. The category is layered for the same reason an operating system is layered — each layer has different requirements, and a tool optimized for one is rarely optimal for another.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.