Our commitment to reliability, availability, and support for your cloud cost optimization workflow.
Higher tiers include stronger guarantees and faster support response.
| Metric | Free | Professional | Enterprise |
|---|---|---|---|
| Uptime SLA | Best effort | 99.9% | 99.95% |
| Support Channel | Community (GitHub) | Dedicated support | |
| Response Time | Best effort | < 24 hours (business days) | < 4 hours (critical) |
| Data Retention | 90 days | 1 year | 2 years |
| Incident Notifications | Status page | Status page + email alerts | Status page + email + phone |
Our API and dashboard are hosted on AWS with multi-AZ redundancy. We target high availability for all paid plans.
Scan results and findings are stored in PostgreSQL with daily automated backups and point-in-time recovery.
We monitor our infrastructure 24/7 with automated alerting. Critical incidents trigger immediate response from our on-call team.
Planned maintenance is scheduled during off-peak hours (weekends, early morning UTC) with at least 48 hours notice for paid plans.
Scan uploads are processed within 60 seconds. Dashboard stats and findings are available immediately after processing completes.
The CCA CLI works offline in air-gapped mode. Online features depend on API availability but the CLI itself has no external dependencies.
If we fail to meet our uptime commitment for Professional or Enterprise plans, you may be eligible for service credits:
| Monthly Uptime | Credit |
|---|---|
| 99.0% - below SLA target | 10% of monthly fee |
| 95.0% to 99.0% | 25% of monthly fee |
| Below 95.0% | 50% of monthly fee |
Credits must be requested within 30 days of the incident. Scheduled maintenance windows are excluded from uptime calculations. Credits are applied to future invoices and do not exceed 50% of the monthly fee.
Enterprise customers can negotiate custom SLA terms, including higher uptime targets, dedicated infrastructure, and custom support agreements. Talk to the founder to discuss your requirements.