Service Level Agreement
Last updated 16 November 2026
This Service Level Agreement (“SLA”) is part of the Terms of Service between you and VOLODS LTD. It sets out the monthly uptime we commit to for each paid instance, and the service credits you get if we miss it.
1. Uptime commitment
| Plan | Monthly uptime | Allowed downtime (30-day month) |
|---|---|---|
| Builder | No commitment | — |
| Pro | 99.5% | about 3 hours 36 minutes |
| Business | 99.9% | about 43 minutes |
| Enterprise | 99.9%, or as set out in your order form | about 43 minutes |
The commitment applies per instance, for each calendar month (UTC) in which the instance is on a paid Pro, Business or Enterprise plan. It doesn’t apply during a free trial.
2. How uptime is measured
Our monitoring checks every instance once a minute from outside the instance. A check fails when the instance doesn’t answer over HTTPS, its services report that they aren’t ready, or its management agent stops reporting.
- Downtime starts at the first of three or more consecutive failed checks and ends at the next successful check.
- Monthly uptime is (minutes in the month − minutes of downtime, excluding the exclusions below) ÷ minutes in the month.
- The dashboard’s activity log and the down and recovered emails record each incident with its times.
3. Service credits
If an instance misses its commitment in a month, you can claim a credit against that instance’s plan fee for the month:
| Monthly uptime | Credit |
|---|---|
| Below the commitment, but at least 99.0% | 10% |
| Below 99.0%, but at least 95.0% | 25% |
| Below 95.0% | 50% |
Credits are applied to your next invoice, aren’t paid out in cash, and are calculated on the plan fee only (not add-ons or usage). Credits for a month are capped at 50% of that instance’s plan fee. Service credits are your sole and exclusive remedy for a failure to meet this SLA.
4. Exclusions
Downtime doesn’t count towards the calculation when it is caused by:
- Scheduled maintenance inside your instance’s maintenance window, or announced at least 48 hours ahead, up to 4 hours a month.
- Actions you or your team take, or ask us to take: restores, plan changes, restarts, stack upgrades you start, deleting or changing projects, and changes made over SSH, MCP or SQL.
- Your instance running out of resources because of your workload (CPU, memory, disk or connections), including reaching a plan quota.
- Third-party services you configure, such as your own SMTP or SMS provider, OAuth providers, DNS for your custom domains, or your own code in Edge Functions.
- Suspension under the Terms of Service, including for non-payment or a breach of the acceptable use policy.
- Events beyond our reasonable control, including attacks we couldn’t reasonably prevent and wide-scale failures of the internet or of our cloud provider’s region.
- Features marked as beta or preview in the dashboard or documentation.
5. Claiming a credit
Email [email protected] within 30 days after the end of the month, with the instance name and the dates and times of the downtime. We’ll check it against our monitoring and reply within 10 business days. Credits that aren’t claimed in time lapse.
6. Changes
We may update this SLA. Changes that reduce the commitment or credits apply from the start of your next billing period after we give you at least 30 days’ notice. Enterprise order forms that set different terms take precedence for that instance.