Loading…
Loading…
Service levels
AGI Managed Cloud is in public alpha. The numbers below are planned targets, not a binding commitment, and they take effect only when a plan agreement says so. Local and BYOK modes have no AGI service in the request path, so there is nothing for us to commit to there.
Planned uptime targets
| Component | Target | Measurement window |
|---|---|---|
| Web (agiworkforce.com) | 99.9% | Monthly |
| API gateway | 99.9% | Monthly |
| Authentication | 99.9% | Monthly |
| Provider passthrough | Inherits the provider’s own SLA | Not measured by us |
| Local and BYOK modes | Not applicable: no AGI service in the path | Not measured |
Planned response times
Plan names match the billing catalogue. Plan pricing is on /pricing; it is not restated here so there is only one source of truth for it.
| Plan | First response target | Channel |
|---|---|---|
| Free | 48 hours | |
| Basic and Pro | 24 hours | Priority email |
| Max 5x, Max 15x, and Team | 8 hours | Priority email |
| Enterprise | 4 hours | Priority email |
Planned service credits
Once paid plans reach general availability, the intended policy is a service credit equal to 10% of the monthly fee for each 0.1% below the uptime target in that month, capped at 50% of the monthly fee. To claim, email contact@agiworkforce.com within 30 days of the incident. Final credit terms would be confirmed in your plan agreement; today no automated credit process exists.
Limits
A reviewer should be able to tell the difference between a commitment and an intention without reading the fine print, so here is the difference. As of 5 August 2026:
| Not contractual | These targets take effect only if and when a plan agreement says so. Until then they describe what we are building toward, and nothing on this page creates an obligation. |
| No measured history | We do not publish historical uptime, and we have no incident archive. The live check on /status is a point-in-time signal covering three dependencies, not an availability record. |
| No tiered support routing | Support requests currently arrive in a single email queue. There is no plan-derived priority routing implemented, so treat the response table above as a plan rather than a description of today. |
| No on-call rotation | There is no 24/7 rotation. Response is best-effort during working hours. |
| No recovery objectives | No recovery point objective, recovery time objective, or restore test evidence has been published. |
| No credit process yet | The credit formula below describes intended policy. No automated credit issuance exists, and final terms would be confirmed in a plan agreement. |
Related