[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-error-budget::en":3,"gloss-cluster-error-budget::en":26,"gloss-next-error-budget::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"error-budget","dev-tools","Error Budget","An error budget is the amount of unreliability you're allowed to spend in a given period — the flip side of a service level objective. If your SLO says the API should succeed 99.9% of the time this month, the remaining 0.1% is your error budget: a concrete allowance of failed requests or downtime. The idea reframes reliability as a resource to spend deliberately rather than a vague goal of \"no outages.\" When the budget has room, you can ship faster and take risks; when it's nearly exhausted, the team slows down and prioritizes stability. For founders, this turns the endless velocity-vs-reliability argument into a data-driven policy that product and engineering agree on in advance. Practical note: set the SLO from what users actually need, not 100% — perfect reliability is infinitely expensive and blocks all shipping. Agree up front on what happens when the budget runs out, so the rule is automatic instead of a fight during an incident.","An error budget is the unreliability you're allowed to spend — the 0.1% left over from a 99.9% SLO — and burning it is what pauses feature work for reliability.",null,[11,14,17,20,23],{"slug":12,"name":13},"dora-metrics","DORA Metrics",{"slug":15,"name":16},"incident-management","Incident Management",{"slug":18,"name":19},"observability","Observability",{"slug":21,"name":22},"rollback","Rollback",{"slug":24,"name":25},"service-level-objective","Service Level Objective (SLO)",[27,31,34,38,41,44,47,50,53,56,59,62],{"slug":28,"category":5,"name":29,"updated_at":30},"agent","Agent","2026-08-24T02:46:36+00:00",{"slug":32,"category":5,"name":33,"updated_at":30},"ai-code-assistant","AI Coding Assistant",{"slug":35,"category":5,"name":36,"updated_at":37},"api-gateway","API Gateway","2026-08-24T02:46:37+00:00",{"slug":39,"category":5,"name":40,"updated_at":37},"api-versioning","API Versioning",{"slug":42,"category":5,"name":43,"updated_at":30},"autonomous-agent","Autonomous Agent",{"slug":45,"category":5,"name":46,"updated_at":37},"blue-green-deployment","Blue-Green Deployment",{"slug":48,"category":5,"name":49,"updated_at":37},"canary-deployment","Canary Deployment",{"slug":51,"category":5,"name":52,"updated_at":37},"chaos-engineering","Chaos Engineering",{"slug":54,"category":5,"name":55,"updated_at":30},"ci-cd","Continuous Integration \u002F Continuous Deployment (CI\u002FCD)",{"slug":57,"category":5,"name":58,"updated_at":37},"circuit-breaker","Circuit Breaker",{"slug":60,"category":5,"name":61,"updated_at":37},"cli","Command-Line Interface (CLI)",{"slug":63,"category":5,"name":64,"updated_at":37},"cloud-development-environment","Cloud Development Environment (CDE)"]