Supabase Self-Hosted
Self-hosted PostgreSQL application backend with authentication, storage, APIs and realtime services.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server image
Runs in
Documented customer environment
Customer-operated PostgreSQL database and containerized backend services
- AWS: Customer cloud account
- Railway: Customer platform workspace
- Vultr: Customer cloud account
- AWS
- Railway
- Vultr
Servers / containers
Operated by
Your team
Customer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Supabase community AWS CloudFormation/CDK deployment ↗ · Source checked 2026-11-21
- Railway: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Self-host Supabase in a Railway project ↗ · Source checked 2026-11-21
- Vultr: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Deploy the Supabase Marketplace application on Vultr Compute ↗ · Source checked 2026-11-21
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server image |
|---|---|
| Infrastructure | Servers / containers The official installation runs PostgreSQL and supporting services through Docker Compose on a Linux server or VPS. This is persistent application infrastructure, even when it exposes functions. |
| Licensing model | Open Source / Open Core The listed self-hosted distribution uses open-source components; the Supabase platform repository is Apache-2.0. Managed-cloud features and paid support are separate from this public self-hosted distribution, and bundled components retain their own licenses. |
| License | Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0 |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The self-hosted Auth service supports external OAuth providers, including a configurable Keycloak issuer. This serves end users of applications built on Supabase; it does not establish organizational SSO for the self-hosted Studio/admin dashboard. Review provider, redirect, signup and administrative access separately.
Self-hosted application-user Auth service; Studio federation excluded · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The upstream docker directory contains the multi-service Compose stack and related environment/configuration files. Follow the self-hosting guide for a matching deployment version and replace secrets.
Self-hosted multi-service stack; not the monthly developer newsletter version · Deployment artifact ↗ (master (moving branch)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
For all components, the guide gives 2 CPU cores, 4 GB RAM and 40 GB SSD as a minimum; 4 cores, 8 GB+ and 80 GB+ SSD are recommended. Optional analytics increases requirements.
Docker stack for development and small-to-medium production; not every workload · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate.
Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.
Category fit
- Backend platforms
- PostgreSQL-based application backend with authentication, APIs, storage, realtime and functions; self-hosting does not include every managed-platform feature.
- Databases & vector
- A PostgreSQL-based application data platform with database APIs, authentication and storage services. This entry covers the self-hosted stack.
Compare within Backend platforms
- Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
- AWS
- Azure
- Google Cloud
- HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
- Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
- Azure
- Google Cloud
- KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
- Northflank
- Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
- AWS
- Azure
- Google Cloud
- Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
- Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Heroku
Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Self-hosting scope and responsibilities ↗supabase.com
- Official Docker deployment ↗supabase.com
- Platform repository license ↗raw.githubusercontent.com
- Self-host Supabase in a Railway project ↗railway.com
- Deploy the Supabase Marketplace application on Vultr Compute ↗docs.vultr.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Supabase community AWS CloudFormation/CDK deployment ↗ · AWS
Community template · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
This project-community template deploys Supabase containers on ECS Fargate with Aurora and Studio on Amplify Hosting. It is an alternative to the upstream Compose layout and does not support pg_graphql/GraphQL. Harden Studio access, review feature differences and operate the AWS resources yourself; this is not managed Supabase.
- Self-host Supabase in a Railway project ↗ · Railway
Provider guide · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
Railway documents a community template for PostgreSQL, authentication, REST, storage, and Studio. The services communicate over private networking in the customer’s Railway project. Railway operates the underlying platform.
- Deploy the Supabase Marketplace application on Vultr Compute ↗ · Vultr
Provider guide · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.
Vultr documents selecting the Supabase application while provisioning a Compute server in the customer’s account. The customer chooses the region and plan and administers the installed stack.
- Supabase community AWS CloudFormation/CDK deployment ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked