Supabase: Self-Hosted Backend Platform

Supabase is an open-source alternative to Firebase built on top of PostgreSQL. With over 97,000 GitHub stars, it provides a complete backend-as-a-service stack including a Postgres database, authentication, instant APIs, edge functions, real-time subscriptions, and file storage. Developers use Supabase to build full-stack applications without managing separate services for each backend concern.

Self-hosting Supabase gives you the full platform running on your own infrastructure with no vendor lock-in and no usage-based pricing.

Key Features

• PostgreSQL database with a built-in table editor and SQL editor in the dashboard
• Instant RESTful and GraphQL APIs auto-generated from your database schema
• Built-in authentication supporting email/password, OAuth providers, and magic links
• Real-time subscriptions via WebSockets for live data updates
• File storage with CDN integration and image transformation pipelines
• Edge functions for serverless compute running Deno at the edge
• Row-level security policies for fine-grained access control directly in Postgres
• Database migrations and branching for development workflows

Why Self-Host Supabase?

Full data ownership. Self-hosting means your database, user credentials, uploaded files, and application data live entirely on your infrastructure. For applications handling regulated data (healthcare, finance, government), this simplifies compliance and eliminates third-party data processing concerns.

No usage limits or surprise bills. Supabase Cloud charges based on database size, bandwidth, storage, and edge function invocations. Self-hosting removes all metered billing. Your costs are fixed to your VPS — run as many API calls, store as many files, and serve as many users as your server can handle.

Custom extensions and configuration. Self-hosting gives you root access to the underlying PostgreSQL instance. Install any Postgres extension (PostGIS, pgvector, TimescaleDB), tune performance parameters, and configure backup strategies that match your exact requirements.

Network isolation. Deploy Supabase inside your private network, behind a VPN, or in an air-gapped environment. Keep your backend APIs accessible only to your application servers without exposing them to the public internet.

System Requirements

Resource	Minimum	Recommended
CPU	2 vCPUs	4+ vCPUs
RAM	4 GB	8 GB
Storage	20 GB SSD	50 GB+ SSD
OS	Ubuntu 22.04+	Ubuntu 24.04

Supabase runs multiple services (PostgreSQL, GoTrue auth, PostgREST, Realtime, Storage, Studio dashboard). The recommended specs ensure smooth operation under moderate load. Storage needs depend on your database size and file uploads.

Getting Started

Deploy Supabase on your VPS using Docker Compose through Dokploy. Our guide covers the full stack setup including PostgreSQL, the Studio dashboard, authentication, and SSL configuration.

Deploy Supabase with Dokploy →

Alternatives

• Appwrite — Open-source backend platform with auth, databases, storage, and functions
• PocketBase — Lightweight backend in a single Go binary with SQLite
• NocoDB — Open-source Airtable alternative that turns databases into smart spreadsheets
• Directus — Headless CMS and data platform wrapping any SQL database with REST and GraphQL APIs

FAQ

Is self-hosted Supabase the same as Supabase Cloud? The core features are identical — you get the same PostgreSQL database, APIs, auth, storage, and real-time engine. Some cloud-specific features like Supabase Branching and managed backups require manual setup when self-hosting. The Studio dashboard is fully included.

Can I migrate from Supabase Cloud to self-hosted? Yes. Since Supabase is built on standard PostgreSQL, you can use pg_dump and pg_restore to migrate your database. Auth users, storage buckets, and edge functions can be exported and imported to your self-hosted instance.

How do I handle database backups? Use standard PostgreSQL backup tools — pg_dump for logical backups or continuous archiving with WAL-G for point-in-time recovery. Schedule automated backups via cron and store them in object storage for redundancy.

Does self-hosted Supabase support multiple projects? Each Supabase instance serves one project by default. For multiple projects, deploy separate instances or use PostgreSQL schemas with separate API configurations. The self-hosted approach gives you full flexibility in how you structure your deployment.

---

App data sourced from selfh.st open-source directory.