Supabase Cloud is Supabase's hosted Postgres development platform, sold in Free, Pro, Team and Enterprise plans; these pages cover moving to self-hosted Supabase, the Apache-2.0 open-source stack run in your own infrastructure.
Same open-source stack, different operator: what Supabase's hosted plans include (per-project compute, backups, PITR, branching, SOC 2 and SLAs) against self-hosting with Docker Compose, one project per Studio, community support and backups you run yourself.
Supabase's documented platform-to-self-hosted path: dumping roles, schema and data with the Supabase CLI, restoring with psql, copying Storage objects with rclone over S3, and reconfiguring JWT keys, auth providers, Edge Functions and domains.
Per-project compute, disk, MAU, egress, PITR and Team plan fees on Supabase Cloud against self-hosted Supabase's servers, storage, backup tooling, upgrades and on-call time, including the managed features you would rebuild or go without.
What you can take out of a Supabase Cloud project and how: logical dumps with the Supabase CLI, Storage files through the S3-compatible endpoint, what daily backups leave out, and what happens to data and backups when a project is deleted.
Comparing Supabase Cloud with Appwrite run on your own servers: Postgres with PostgREST against Appwrite's databases, auth, storage and functions, realtime, multi-project support that self-hosted Supabase lacks, and the operating work of each.
Using Appwrite Migrations to import users, databases and files from Supabase, what it moves partially (rows) or not at all (functions), rewriting Postgres-specific logic, and running the target Appwrite self-hosted or on Appwrite Cloud.
Supabase Cloud projects run in one AWS region, including several in the EU. This page compares that with self-hosted Supabase in an EU data center or sovereign cloud you choose, and the logging, backups and support you take on.
Supabase sells HIPAA as a paid add-on from the Team plan. This page weighs that against self-hosted Supabase in your own audited environment: which safeguards you then own, logging, backups and encryption, and what the community-supported stack lacks.
Self-hosted Supabase has no managed backups or point-in-time recovery. This page covers rebuilding them with pg_dump, WAL archiving and tested restores, or by running the database on CloudNativePG or Patroni, plus Storage object backups.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.