Self-Hosting | Supabase 日本語

Self-hosting is a good fit if you need full control over your data, have compliance requirements that prevent you from using managed services, or want to run Supabase in an isolated environment.

Get started

The fastest and recommended way to self-host Supabase is to use Docker.

Docker: Deploy Supabase within your own infrastructure using Docker Compose.

Community projects

These projects are maintained by the Supabase community, not by Supabase. To get involved, see the Community page.

Kubernetes: Run Supabase on Kubernetes with the Supabase Operator or a Helm chart.
Observability: Collect logs, metrics, and traces from self-hosted Supabase with open-source tools.

How self-hosted Supabase differs

Self-hosted Supabase runs as a single project, which means that Studio doesn't support multiple organizations or projects. Most settings are configured through environment variables.

Some features of the managed platform aren't available when self-hosting: branching, advanced metrics beyond logs, managed backups and PITR, analytics and vector buckets, ETL, and the Management API. To collect logs and metrics yourself, see the community-maintained observability project.

Not the same as local development

Supabase CLI runs a local stack for development and testing. That stack is not a self-hosted deployment: it is not hardened for production and must not be exposed to external traffic.

To self-host, use Docker or the community-maintained Kubernetes project.

Your responsibilities when self-hosting

When you self-host, you are responsible for:

Server provisioning and maintenance
Security hardening and keeping OS and services updated
Service configuration and management
Postgres database maintenance
High availability and scalability
Backups and disaster recovery
Monitoring and uptime

Third-party guides

Guides written by other projects and companies. Supabase doesn't maintain them, so check that they match your version of self-hosted Supabase.

Secure self-hosted Supabase with NetBird: Keep Studio and Postgres off the public internet with NetBird network access controls.

Telemetry

Self-hosted Supabase does not phone home or collect any telemetry.

The Supabase CLI, a separate tool also used for local development, collects usage telemetry to help improve the developer experience. See CLI telemetry for opt-out methods.

Support and community

Self-hosted Supabase is community-supported.

GitHub Discussions: Ask questions, resolve common issues, and make feature requests
GitHub Issues: Find out about known issues and workarounds
Discord: Connect with other users and get help
Reddit: Join the official Supabase subreddit
Share your experience: Share your self-hosting experience

Enterprise self-hosting

If you're an enterprise using self-hosted Supabase, we'd love to hear from you. Reach out to our Growth Team to discuss your use case, share feedback, or explore design partnership opportunities.