Self-Hosting

Self-Hosting

Install and run your own Supabase on your computer, server, or cloud infrastructure.


Get started#

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

Community-driven projects#

There are several other options to deploy Supabase. If you're interested in helping these projects, visit our Community page.

About self-hosting#

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

How self-hosted Supabase differs#

Self-hosted Supabase is different from:

  • Supabase CLI (local development), which is intended for development and testing only.
  • Managed Supabase platform, which is fully hosted and operated by Supabase.

Telemetry#

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

The Supabase CLI is a separate tool from self-hosted Supabase and collects usage telemetry to help improve the developer experience. You can opt out by running supabase telemetry disable or setting SUPABASE_TELEMETRY_DISABLED=1. See CLI telemetry for other opt-out methods.

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
  • Maintaining the Postgres database
  • Backups and disaster recovery
  • Monitoring and uptime

Support and community#

Self-hosted Supabase is community-supported.

For resolving common issues:

Get help and connect with other users:

  • Discord - Real-time chat and community support
  • Reddit - Official Supabase subreddit

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.