How-to guides
Self-hosting Supabase vs a managed dedicated server
Teams self-host Supabase to keep data on their own hardware and control costs. The software is open source; operating it well is the hard part.
What you take on when self-hosting
- Running the Docker Compose stack and keeping its services healthy
- Upgrading Postgres and each service without breaking compatibility
- Backups, offsite copies and point-in-time recovery
- TLS, secrets, SMTP for auth emails, and monitoring
- Some hosted-only dashboard features aren’t available
What Da8a does instead
Da8a gives you a Supabase-compatible backend on a server dedicated to you and operates it: backups, PITR, upgrades and a dashboard with an approve-first assistant. Your code keeps using supabase-js.
| Self-hosted Supabase | Da8a | |
|---|---|---|
| Data on a dedicated server | Yes | Yes |
| Who operates it | You | Da8a |
| Backups + PITR | Set up yourself | Included |
| Import from Supabase | Manual | Guided, server to server |
Moving
Import an existing Supabase or self-hosted project, then swap the URL and anon key. See Da8a vs self-hosted Supabase.
Questions
Is Da8a a fork of Supabase?
Da8a is compatible with the Supabase APIs and the official supabase-js client; you don’t install anything different in your app.
Related
- Row Level Security (RLS) explained with examples
- Add Google and GitHub sign-in with supabase-js
- Passwordless magic link login
- Semantic search with pgvector
- Quickstart
- supabase-js client docs
Updated 2026-10-23.