The Operate pillar

Run what you ship from one place.

Once code is in production, the questions change. How often do you ship, and how long does a fix take? Is this service inside its reliability budget? What broke, and what did it cost? Operate brings DORA metrics, SLOs, incidents, runbooks, observability, and cost into one view, tied to the service each team already owns. You connect the tools you run today. IntegraCI reads from them and puts the answers next to the work.

Service level objectives

Spend your error budget on purpose.

An SLO is only useful if the team can see it the moment it slips. Set the target per service, and IntegraCI tracks the budget against it and warns when the burn rate climbs, so reliability is a decision you make rather than a surprise you absorb.

• Targets you set, not guesses

  Define the objective per service. The platform measures against it and shows remaining error budget, so you know how much room you have before the next change spends it.

• Burn you can see early

  When a service starts eating its budget faster than planned, it surfaces while you can still act, not after the page fires.

• Tied to the service, not a dashboard

  Each objective lives on its catalog entry, so the owner sees their own reliability without hunting through a shared board.

Runbooks

Make the 2am fix a procedure, not a memory test.

The steps that resolve a known problem should be written down, reviewed, and runnable. Runbooks are versioned procedures that pause for a human approval before anything risky touches production, and log every run, so the next person on call inherits a record instead of a rumour.

• Steps as code

  A runbook is a versioned, reviewed procedure, not a wiki page someone forgot to update. It runs the same way every time.

• Approvals where they matter

  Steps that touch production pause for a human approval through the same gate the rest of the platform uses. Nothing risky runs unwatched.

• A record of every run

  Each execution is logged: who ran it, what it did, and the result. The next on-call engineer reads the history instead of guessing.

Cost & FinOps

Put the cloud bill where someone can act on it.

A spend number nobody owns never goes down. IntegraCI attributes cost back to the team and service that drives it, flags where spend looks off, and exports clean per-tenant breakdowns for chargeback, so the people who can change the bill are the ones looking at it.

• Spend mapped to owners

  Cost is attributed back to the team and service that drives it, so the bill is something a team can act on rather than a lump sum.

• Optimisation surfaced, not forced

  The platform flags where spend looks off and suggests where to look. You decide what to change.

• Chargeback ready

  Per-tenant and per-service breakdowns export cleanly, so finance gets numbers they can reconcile.