Last updated: March 2026
All plans include high-availability infrastructure — multi-node redundancy, automatic failover, and 2-replica WordPress by default.
| Plan Tier | Monthly Uptime Target | Max Downtime/Month |
|---|---|---|
| Starter | 99.9% | ~43 minutes |
| Professional | 99.9% | ~43 minutes |
| Business | 99.95% | ~22 minutes |
| Enterprise | 99.95% | ~22 minutes |
All plans use multi-node redundancy: Docker Swarm auto-reschedules on node failure, MariaDB Galera provides 3-node synchronous replication, GlusterFS provides 3-way replicated storage.
((total_minutes - downtime_minutes) / total_minutes) × 100| Layer | Redundancy | Failover |
|---|---|---|
| Web/App | Docker Swarm (2 replicas on all plans) | Auto-reschedule on node failure (~30s) |
| Database | MariaDB Galera (3-node synchronous replication) | Automatic via Galera cluster consensus |
| Storage | GlusterFS (3-way replicated across all nodes) | Transparent to application |
| SSL/Proxy | Traefik with automatic Let's Encrypt | Certificate auto-renewal |
| Monitoring | Prometheus + Blackbox + Grafana | Automated alerting |
If verified downtime exceeds the committed uptime target in a calendar month:
| Excess Downtime | Service Credit |
|---|---|
| Up to 1 hour beyond SLA | 5% of monthly fee |
| 1-4 hours beyond SLA | 10% of monthly fee |
| 4-12 hours beyond SLA | 25% of monthly fee |
| Over 12 hours beyond SLA | 50% of monthly fee |
Maximum credit: 50% of the monthly fee for the affected service in the affected month.
How to claim: Contact support within 30 days of the incident. Include the affected site domain and the approximate time window. We will verify against our monitoring data.
We may update this SLA from time to time. Changes will be announced via email to active subscribers at least 30 days before taking effect. The current version is always available on this page.