Self-Hosting Overview

Run Supabase on your own infrastructure with full control and customization

Self-hosting Supabase gives you complete control over your data and infrastructure. Deploy the entire Supabase stack on your own servers, cloud provider, or on-premise datacenter.

Why Self-Host?

Data Sovereignty

Keep all data within your infrastructure and jurisdiction. Meet strict compliance requirements.

Cost Control

Optimize costs for high-scale applications by using your existing infrastructure.

Customization

Modify and extend Supabase components to fit your specific needs.

Air-Gapped Deployment

Run completely offline for maximum security in restricted environments.

What You Get

Self-hosted Supabase includes all core components:

• Supabase Studio - Web dashboard for database management
• PostgreSQL - Industry-leading relational database
• PostgREST - Automatic REST API from your database schema
• GoTrue - JWT-based authentication and user management
• Realtime - WebSocket server for database change notifications
• Storage API - S3-compatible file storage with image transformations
• Kong - API gateway for routing and security
• Edge Runtime - Run Deno-based serverless functions
• Logflare - Log aggregation and analytics
• Supavisor - Connection pooler for Postgres

Architecture

System Requirements

Minimum Requirements

For development/testing:

• CPU: 2 cores
• RAM: 4 GB
• Storage: 20 GB SSD
• OS: Linux (Ubuntu 20.04+, Debian 11+, or RHEL 8+)
• Software: Docker 20.10+ and Docker Compose 2.10+

Recommended for Production

For production workloads:

• CPU: 4+ cores (8+ for high traffic)
• RAM: 8 GB minimum (16 GB+ recommended)
• Storage: 100 GB SSD (scales with data)
• Network: 1 Gbps connection
• Backup: Separate volume for database backups

The default configuration is NOT secure for production. You must change all default passwords and secrets before deploying.

Deployment Options

Docker Compose (Recommended)

The easiest way to self-host Supabase:

Kubernetes

For production-grade deployments:

Official Kubernetes Helm charts are in development. For now, use Docker Compose for production or build custom K8s manifests.

Cloud Providers

Deploy on popular cloud platforms:

• AWS: EC2, ECS, or EKS
• Google Cloud: Compute Engine or GKE
• Azure: Virtual Machines or AKS
• Digital Ocean: Droplets or Kubernetes
• Linode: Compute instances
• Hetzner: Dedicated or cloud servers

On-Premise

Deploy in your own datacenter:

• Physical servers
• VMware or Proxmox VMs
• Private cloud infrastructure
• Air-gapped environments

Feature Comparison

Self-hosted vs. Supabase Cloud:

Feature	Self-Hosted	Supabase Cloud
Database	Full Postgres access	Full Postgres access
Authentication	✅ All providers	✅ All providers
Storage	✅ S3-compatible	✅ Managed S3
Realtime	✅ Full feature set	✅ Full feature set
Edge Functions	✅ Self-managed	✅ Global deployment
Studio Dashboard	✅ Included	✅ Enhanced UI
Automatic Backups	⚙️ Configure yourself	✅ Automated daily
Point-in-Time Recovery	⚙️ WAL archiving required	✅ 7-day window
Automatic Scaling	❌ Manual	✅ Automatic
DDoS Protection	⚙️ Configure yourself	✅ Included
CDN	⚙️ Configure yourself	✅ Global CDN
Monitoring	⚙️ Logflare included	✅ Enhanced metrics
Support	💬 Community	📧 Email + Priority
Updates	⚙️ Manual	✅ Automatic
Multi-Region	⚙️ Configure yourself	✅ Simple setup
SOC 2 Compliance	⚙️ Your responsibility	✅ Certified

Getting Started

Choose your deployment method:

Docker Compose

Quick start guide for Docker-based deployment

Configuration

Environment variables and settings

Security

Secure your self-hosted installation

Updates

Keep your stack up-to-date

Support & Community

Self-hosted Supabase is community-supported. Managed support is available on Enterprise plans.

Community Resources

GitHub Discussions:

• Self-Hosting Questions
• What’s Working (and What’s Not)

GitHub Issues:

• Report Bugs
• Feature Requests

Discord:

• Join discord.supabase.com
• #self-hosting channel for questions
• Active community of self-hosters

Reddit:

• r/Supabase community
• Share experiences and solutions

Enterprise Support

For production self-hosted deployments:

• Dedicated support channel
• Architecture review and recommendations
• Custom SLAs available
• Migration assistance from other platforms
• Training for your team

Contact [e-mail] for details.

Limitations & Considerations

Manual Updates Required

You’re responsible for applying updates and security patches. Monitor the changelog regularly.

No Automatic Scaling

Self-hosted deployments don’t auto-scale. Plan capacity based on expected traffic and monitor resource usage.

Backup & Disaster Recovery

Implement your own backup strategy, test restore procedures, and plan for disaster recovery scenarios.

Security Hardening

You’re responsible for securing the infrastructure, applying patches, managing secrets, and configuring firewalls.

Operational Expertise

Requires knowledge of Docker, PostgreSQL, networking, and Linux system administration.

Migration Paths

From Supabase Cloud to Self-Hosted

1. Export Data

   Use pg_dump to export your database schema and data.

2. Download Storage Files

   Backup all files from Storage buckets.

3. Deploy Self-Hosted

   Set up your self-hosted instance.

4. Import Data

   Restore database and storage files.

5. Update Connection Strings

   Point your applications to new self-hosted instance.

From Self-Hosted to Supabase Cloud

Contact [e-mail] for assisted migration to Supabase Cloud.

Next Steps

1. Install with Docker

   Follow the Docker installation guide to deploy Supabase in minutes.

2. Configure Services

   Review configuration options and customize for your environment.

3. Secure Your Installation

   Follow security best practices before going to production.

4. Set Up Updates

   Create an update strategy to keep your stack current.