1 open incident
Checkout API — SLO “Checkout Latency” is RED
View details

Safe-to-Deploy · SLA-aware

Uses features you already have

SLA-aware deployment decisions

Combine your existing SLOs and SLAs so Safe-to-Deploy decisions reflect customer impact, not just raw metrics.

What you can do today

  1. Define SLOs for each service: open SLOs
  2. Create SLAs that point at those SLOs and represent key customers: open SLAs
  3. Use the Safe-to-Deploy API / UI to see how SLO health affects the deploy decision: Safe-to-Deploy docs

Roadmap: deeper SLA-aware policy

Next iteration will let you:

  • • Attach SLA tiers to deployment risk policy.
  • • Block risky deploys only for premium customers.
  • • Generate reports showing which SLAs were protected.
← Back to Safe-to-Deploy cockpit