# What is SupaHost

> SupaHost runs the open-source Supabase stack on your own cloud VM, with many projects per instance for one flat monthly price. What you get, what differs and where to start.

Source: https://supahost.app/docs/getting-started/introduction · Updated 2026-11-11

SupaHost is managed hosting for open-source Supabase. You get an **instance**, which is a cloud VM that belongs to you alone, and on it you create as many **projects** as your plan allows. Each project is an ordinary Supabase project: its own Postgres database, Auth, Data API, Storage, Realtime, Edge Functions, URL and API keys.

Because each project speaks the same APIs as Supabase, the official client libraries (supabase-js, supabase-py, supabase_flutter, supabase-swift, supabase-kt and others) work without changes. You point them at your SupaHost project URL and use your project's keys.

## What you get

Every project on an instance includes:

| Part | What it is |
|---|---|
| Database | Postgres 17, one database per project |
| Data API | PostgREST, the auto-generated REST API over your tables |
| Auth | Email and password, magic links, 19 OAuth providers, anonymous sign-ins, TOTP MFA |
| Storage | Buckets and files with Row Level Security, up to 50 MB per file |
| Realtime | Broadcast, Presence and Postgres Changes |
| Edge Functions | Deno functions, deployed from the dashboard or by an AI agent over MCP |
| Cron and Queues | pg_cron built in, plus pgmq queues |
| Studio | Supabase Studio for each project, opened from the SupaHost dashboard |

On top of that, SupaHost runs the parts you would otherwise have to operate yourself: daily database backups, point-in-time recovery on Pro and above, health checks every minute with email alerts, disks that grow as they fill, HTTPS on custom domains, and an [MCP server](/docs/ai-tools/mcp) so AI coding tools can work with your projects.

## How pricing works

You pay one flat monthly price per instance. There are no charges per monthly active user, per Realtime connection or message, or per Edge Function invocation. Database size, file storage and egress are pooled across all projects on the instance.

| Plan | Price per month | Projects included | Server |
|---|---|---|---|
| Builder | $25 ($20 billed annually) | 5 | 2 shared vCPU, 4 GB RAM |
| Pro | $49 ($39 billed annually) | 15 | Dedicated 2 vCPU, 8 GB RAM |
| Business | $99 ($79 billed annually) | 30 | Dedicated 4 vCPU, 16 GB RAM |
| Enterprise | Custom | Custom | Custom |

Extra projects cost $3 per month each. See [Plans and limits](/docs/platform/plans) for storage, egress, backups and the rest. New accounts start with a 7-day free trial (card required, up to 3 projects during the trial).

## Your code stays the same

A project on instance `acme` named `app-one` lives at `https://app-one.acme.supahost.space`. This is all it takes to query it from JavaScript:

```ts
import { createClient } from '@supabase/supabase-js'

const supabase = createClient(
  'https://app-one.acme.supahost.space',
  process.env.SUPABASE_ANON_KEY!
)

const { data, error } = await supabase.from('recipes').select('id, title')
```

The same is true for Auth, Storage, Realtime and Functions calls. If you are moving an existing Supabase Cloud project, you change the URL and keys, and the one-click [import](/docs/platform/import-from-supabase) copies your database, users and files.

## Where SupaHost differs from Supabase Cloud

SupaHost runs the open-source stack, so some Supabase Cloud features aren't there. The main ones:

- **No direct database connection on most plans.** Postgres isn't exposed to the internet. Business and Enterprise get a restricted SSH tunnel for tools like psql, pg_dump and ORM migrations. On other plans you use the Data API, Studio's SQL editor, the MCP server or exports.
- **No connection pooler (Supavisor) and no read replicas.**
- **No Supabase CLI deploys.** The CLI works for local development, but `supabase link`, `supabase db push` against a linked project and `supabase functions deploy` rely on Supabase's Management API, which SupaHost doesn't offer. See [Local development](/docs/local-development/overview).
- **No phone or SMS auth, no custom SMTP.** Auth emails are sent for you from `noreply@supahost.app` using templates you can edit.
- **No image transformations** in Storage, and Storage files aren't part of the daily database backups (you can download them any time).
- **No searchable log explorer** in the dashboard, and Studio's Logs and Reports pages aren't available. Edge Function logs are on the Functions tab.
- **Legacy API keys only.** Each project has an `anon` and a `service_role` key; there are no publishable or secret keys, and keys can't be rotated.

The full list, product by product, is in [Supabase features on SupaHost](/docs/getting-started/feature-support).

## Is it a good fit?

SupaHost suits teams and solo developers who run several Supabase projects, or one busy one, and want a predictable bill without managing servers. Projects never pause for inactivity.

It isn't the right choice if you need SOC 2, ISO 27001 or HIPAA compliance, a contractual SLA, multi-server failover or read replicas. SupaHost is in public beta.

SupaHost is run by Volods LTD, a company registered in England and Wales, and isn't affiliated with Supabase Inc.

## Next steps

- [Quickstart: your first project in 5 minutes](/docs/getting-started/quickstart)
- [Instances, projects and the stack](/docs/getting-started/architecture)
- Framework guides: [Next.js](/docs/getting-started/nextjs), [React](/docs/getting-started/react), [Flutter](/docs/getting-started/flutter), [Python](/docs/getting-started/python) and more in this section