Skip to content
SupaHost
  • The Supabase stack
    PostgresPostgreSQL 17 with RLS and every Supabase extensionAuthEmail, 19 OAuth providers and MFA, no MAU feesRealtimeBroadcast, Presence and Postgres Changes, no per-connection feesEdge FunctionsDeno functions with no per-call feesStorageBuckets with RLS and resumable uploadsBackups & PITRDaily backups, point-in-time restore on Pro+Custom domainsFree subdomain plus your own, with automatic SSL
    Platform
    Multi-project instancesUp to 30 isolated projects on one planYour own VMEvery instance runs on its own VMAI coding agentsMCP for Claude Code, Cursor, Codex and VS Code>_SSH & direct Postgrespsql, logs and a Postgres tunnel (Business+)
  • By stage
    Side projectsBuilder — 5 projects on a small VM, $25/moProduction appsPro — 15 projects on a dedicated VM, $49/moGrowing teamsBusiness — 30 projects, SSH, 14-day PITREnterpriseCustom limits, regions and terms
    Use cases
    AgenciesEvery client project on one flat-priced planSaaS productsProduction, staging and dev on one billAI appspgvector embeddings on your own PostgresMobile appsAuth with no per-user fees, at a flat price
  • Learn
    All featuresEverything included on every planDocumentationEvery Supabase feature on SupaHostGuidesSupabase pricing, hosting, backups and moreKnowledge baseSupabase errors explained, with fixesQuickstartFrom signup to your first projectCustom domainsCNAME, verify, automatic SSLMCP serverTools and setup for AI coding agents
    Pricing
    Compare plansEvery feature on every planSupabase pricing calculatorEstimate a Supabase Cloud billvs Supabase CloudPer-project pricing vs one flat planMigrate from Supabase CloudOne-click import and a savings calculatorAdd-onsExtra domains, storage, bandwidth and compute
  • Pricing
  • Docs
  • Log in
Log inStart free
Legal

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

PlanMonthly uptimeAllowed downtime (30-day month)
BuilderNo commitment—
Pro99.5%about 3 hours 36 minutes
Business99.9%about 43 minutes
Enterprise99.9%, or as set out in your order formabout 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 uptimeCredit
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.

SupaHost

Product

All featuresMulti-project instancesAI coding agents (MCP)Custom domainsBackups & PITRPricing

Solutions

AgenciesSaaS productsAI appsMobile appsvs Supabase CloudMigrate from Supabase Cloud

Resources

DocsKnowledge baseGuidesSupabase pricing calculatorQuickstartMCP serverCompare plans

Company

AboutContactPrivacy PolicyTerms of ServiceSLA

© 2026 Volods LTD. All rights reserved.

SupaHost is a product of VOLODS LTD, registered in England and Wales, company number 16149306. Registered office: 29 Rosemary Avenue, Grimsby, England, DN34 4JN.
Supabase is a trademark of Supabase, Inc. SupaHost is independent and not affiliated with Supabase, Inc.