# Are all Supabase features available on SupaHost?

> Most Supabase features work on SupaHost as they do on Supabase Cloud. A quick list of what works, what works differently, and what isn't available, with links to details.

Source: https://supahost.app/kb/self-hosted-feature-differences · Updated 2026-11-11

Most of them. SupaHost runs the open-source Supabase stack, so the database, Auth, Data API, Storage, Realtime, Edge Functions, Cron and Queues all work with the normal client libraries. A handful of features are different or missing, mostly ones that rely on extra services Supabase Cloud runs alongside the core stack (the connection pooler, log analytics, image transformations). The full table is on [Supabase features on SupaHost](/docs/getting-started/feature-support).

## Works as on Supabase Cloud

- **Postgres 17**, with the extensions the Supabase Postgres image ships, including pgvector, PostGIS, pg_net and pgmq.
- **Data API** (PostgREST): queries, filters, RPC, generated types.
- **Auth**: email and password, magic links and email OTP, 19 OAuth providers, anonymous sign-ins, TOTP MFA, Row Level Security with `auth.uid()`.
- **Storage**: buckets, policies, public and signed URLs, files up to 50 MB.
- **Realtime**: Broadcast, Presence and Postgres Changes.
- **Edge Functions** (Deno) with `npm:`, `jsr:` and `https:` imports.
- **Studio**: table editor, SQL editor, Auth users, Storage browser, policies, database tools and API docs.

## Works, but differently

| Feature | On SupaHost |
|---|---|
| Edge Function deploys | From the dashboard's **Functions** tab or over MCP, not `supabase functions deploy` |
| pg_cron | Built in; don't run `create extension pg_cron`. Managed on the **Cron** tab or in SQL |
| Auth emails | Sent by SupaHost from `noreply@supahost.app` with your app name; templates are editable; no custom SMTP |
| API keys | Legacy `anon` and `service_role` JWT keys only; no rotation |
| Direct Postgres | Business and Enterprise only, through an SSH tunnel |
| Branching | Pro and up; a branch is a copy of a project, with or without data, and there's no merge |
| Backups | Daily database backups, plus point-in-time recovery on Pro and Business. Storage files aren't in backups, but can be exported any time |
| Logs | Edge Function logs in the dashboard; no Studio log explorer |
| Exposed schemas | Fixed: `public`, `storage`, `graphql_public`, `pgmq_public` |
| Projects | Many projects share one instance (your own VM), and one flat price |

## Not available

- Connection pooler (Supavisor) and read replicas
- Phone and SMS sign-in, and phone MFA
- Image transformations and the Storage S3 protocol
- GraphQL over HTTP (no `/graphql/v1` endpoint)
- Studio's Logs and Reports pages
- The Supabase Management API, so CLI commands such as `link`, `db push` and `secrets set` don't work
- Custom SMTP for Auth emails
- SOC 2, ISO 27001 or HIPAA certification, an SLA, or multi-server failover

SupaHost is in public beta.

## What this means in practice

If your app uses supabase-js (or the Flutter, Swift, Kotlin or Python client) against the Data API, Auth, Storage and Realtime, you change the URL and keys and it works. The things to plan for are:

- apps that rely on a pooled connection string for serverless ORMs;
- SMS sign-in;
- on-the-fly image resizing;
- a deploy pipeline built on `supabase functions deploy` or `supabase db push`.

Check those against the feature table before you move.

## Related

- [Supabase features on SupaHost](/docs/getting-started/feature-support)
- [Supabase CLI commands that don't work with SupaHost](/kb/cli-forbidden-or-unsupported)
- [Images without transformations](/docs/storage/images)
- [Is SupaHost real Supabase?](/kb/is-it-really-supabase)