Self-Hosted Supabase
Self-hosting gives you control over where your data lives and what you pay for. It also makes you responsible for security, backups and updates. We set it up properly and show you exactly what you're taking on.
Your app
Cloudflare (DNS / TLS) · your account
Reverse proxy (Caddy / Nginx) · your account
Supabase stack: API gateway, Auth, PostgREST, Realtime, Storage, Studio
Postgres · your account
Offsite backups (S3 / R2) · Monitoring and alerts
We'll tell you on the call if Supabase Cloud is the better choice for you. Sometimes it is.
Server sized for your workload in your account (Hetzner, DigitalOcean, AWS, Hostinger VPS or similar), OS hardened, firewall, SSH keys only.
Supabase via the official Docker Compose setup, pinned to a release.
Every secret and key generated fresh; nothing left at example defaults.
HTTPS through a reverse proxy, your domain via Cloudflare DNS.
Studio and Postgres not exposed to the public internet; dashboard protected.
Auth configured: site URL, redirect URLs, custom SMTP, email templates.
Storage on local disk or S3-compatible object storage (S3, R2).
Connection pooling configured for your app.
Automated offsite database backups, and a restore test we run with you.
Uptime and resource monitoring with alerts to your inbox.
Update procedure documented and tested once.
Runbook: start/stop, logs, rotate keys, restore, update.
We can migrate schema, data, auth users and storage files to your self-hosted instance and switch your app over with a planned cutover. Migration is scoped separately because it depends on data size and downtime tolerance.
We look at the workload, the region, and whether Cloud is actually the better fit.
A written scope and one quote before any commitment.
The stack, TLS, secrets, and access limits live in accounts you own.
We restore a backup with you and leave the steps in writing.
Self-hosted Supabase needs regular updates and backup checks. Managed Infrastructure Care covers that every month, or your team can follow the runbook.
FAQ
Sometimes, often not once you count your time. We'll compare both honestly for your workload. Choose self-hosting for control first.
A self-hosted instance runs a single project, and platform features such as managed backups, point-in-time recovery and branching are not included. We replace what we can (backups, monitoring) and tell you what remains different.
Supabase's documented minimum is 4 GB RAM, 2 CPU cores and 40 GB SSD; 8 GB RAM and 4 cores is the recommended starting point. We size it for your actual load.
You own the server and all credentials. We use a named key you can remove at any time.
We deploy your app to hosting you own, on the same server or a platform like Vercel or Cloudflare. We don't host client apps on our own servers.
Supabase publishes updated self-hosted releases regularly. We document the update procedure and can run updates for you on Care.
Next step
Book a free 30-minute call, or send your app for a free written assessment. Either way, you'll have a clear scope and a written quote before you pay anything.
Custom quote after a free assessment · Work happens in your accounts · Written handover
