Self-hosted Supabase: what it takes to run it in production
You can run Supabase on your own servers, and Supabase's docs say what you then own: every service in the stack, and the Postgres underneath it. This guide lists both, from the docs, with the dates read.
- ✓Docs read 17 Nov 2026
- ✓OSStend does not run Supabase
Yes, you can self-host Supabase: it runs on your own server or cloud with Docker Compose, and Supabase's docs list server provisioning, Postgres maintenance, high availability, backups and monitoring as your responsibility. Managed backups and point-in-time recovery are not part of the self-hosted edition. Docs read 17 Nov 2026.
Can you self-host Supabase?
Yes. Supabase describes self-hosting as installing and running your own Supabase on your computer, server or cloud infrastructure, and calls Docker Compose the fastest and recommended route. It is a good fit, per the docs, when you need full control of your data, have compliance rules that rule out managed services, or want an isolated environment.
| Question | What Supabase's docs say | Source, checked |
|---|---|---|
| How is it deployed? | Docker Compose is the official route; Kubernetes (an operator or a Helm chart) is listed as community-maintained, not Supabase-maintained | Self-hosting overview, checked 17 Nov 2026 |
| What does it need? | Linux server administration, git, Docker and Docker Compose, and networking basics. Minimum 4 GB RAM, 2 cores and a 40 GB SSD; recommended 8 GB or more, 4 cores or more and 80 GB or more | Docker guide, checked 17 Nov 2026 |
| How many projects? | One. Self-hosted Supabase runs as a single project, so Studio has no multiple organizations or projects | Self-hosting overview, checked 17 Nov 2026 |
| Who supports it? | The community: GitHub Discussions, GitHub Issues, Discord and Reddit. Enterprises are invited to contact Supabase's growth team | Self-hosting overview, checked 17 Nov 2026 |
| How often does it change? | Stable snapshots of the Docker Compose setup are published about once a month | Docker guide, checked 17 Nov 2026 |
How we wrote this: Supabase's self-hosting docs and pricing page, read on 17 Nov 2026. We did not install it or run a benchmark, and we quote no performance figure. Supabase's own pages change, so check the linked page before you plan a build.
Which services does a self-hosted Supabase run?
The stack is thirteen components, and the default setup starts most of them. Studio, the API gateway, Auth, PostgREST, Realtime, Storage, imgproxy, postgres-meta, Postgres, Edge Runtime and the Supavisor pooler are the working set. Logflare and Vector for logs are optional.
| Component | What the docs say it does | Running it means |
|---|---|---|
| Studio | A dashboard for managing your self-hosted project; protected by HTTP basic authentication | Setting a strong dashboard password and keeping Studio off the open internet |
| Envoy (Kong optional) | The API gateway; listens on port 8000 by default | Putting TLS in front of it with a reverse proxy such as Caddy or Nginx |
| Auth | JWT-based authentication for sign-ups, logins and sessions | Holding the JWT keys and an SMTP server; social, phone and SSO sign-in each have their own setup guide |
| PostgREST | Turns the Postgres database into a REST API | Keeping its schema and role configuration in step with the database |
| Realtime | An Elixir server that listens to Postgres changes and broadcasts them to clients | Its own encryption key and the database settings it relies on |
| Storage and imgproxy | A REST API for files in S3 with Postgres handling permissions, plus image processing | Local disk by default, or an S3-compatible backend you connect and back up |
| postgres-meta | A REST API for managing Postgres | A crypto key for the connection strings Studio uses |
| Postgres | The database. Several services need specific roles and configuration inside it | Everything in the next section |
| Edge Runtime | A Deno-based server for functions | Function code on disk, restarts to pick up changes |
| Supavisor | The connection pooler; session mode on port 5432, transaction mode on 6543 | Pool sizes that fit Postgres's connection limit |
| Logflare and Vector | Log management and log collection; not in the default configuration | Extra memory and an override file if you want logs in Studio |
Source: the architecture list, system requirements and service sections of the Docker guide, checked 17 Nov 2026. The right column is our reading of what each item asks of your team.
From our on-call engineers: what we change before a self-hosted Supabase starts
A self-hosted Supabase is a stack of containers around one Postgres, and its safe defaults are placeholders. Everything below is settled before the first start, because rotating secrets afterwards touches every service.
- ✓The Docker stack runs Studio, an API gateway, Auth, PostgREST, Realtime, Storage, imgproxy, postgres-meta, Postgres, Edge Runtime and Supavisor, with Logflare and Vector as optional extras.
- ✓The guide says never to start with the placeholder values in .env.example; the dashboard password, Postgres password, API keys, JWT signing keys and several encryption keys all need generated values first.
- ✓Production traffic goes through an HTTPS reverse proxy such as Caddy or Nginx, and secrets belong in a secrets manager, not in version control.
- ✓Updates use the project's update.sh three-way merge, stable snapshots are published about monthly, and changing individual image tags is not guaranteed compatible.
- ✓The self-hosting guide does not cover backups, and reset.sh deletes the database and storage data, so backup and restore of Postgres and storage objects is something you design yourself.
How do you set up self-hosted Supabase for production?
Provision a Linux server at or above Supabase's recommended size, pull the Docker configuration at a pinned release, generate the secrets and keys, set the public URLs, put a TLS reverse proxy in front, then start the stack. The commands below follow Supabase's manual install.
git clone --depth 1 --branch self-hosted/v0.8.4 https://github.com/supabase/supabase mkdir supabase-project cp -rf supabase/docker/. supabase-project cd supabase-project && cp .env.example .env sh utils/generate-keys.sh sh utils/add-new-auth-keys.sh # edit .env: SUPABASE_PUBLIC_URL, API_EXTERNAL_URL, SITE_URL, SMTP_* sh run.sh start docker compose ps
Version tag as shown in the guide on 17 Nov 2026; use the tag the guide shows when you build. The docs warn never to start with the placeholder passwords and keys in .env.example, and to keep secrets in a secrets manager in production (Docker guide, checked 17 Nov 2026). The Docker guide also says production, especially with OAuth providers, needs HTTPS with a valid certificate, and recommends a reverse proxy such as Caddy or Nginx (reverse proxy guide, checked 17 Nov 2026).
Size the server
At least 4 GB RAM, 2 cores and a 40 GB SSD for development and small to medium production; the docs recommend 8 GB or more, 4 cores or more and 80 GB or more.
Install at a pinned release
Use the quick-start script on a supported Linux distribution, or the manual clone above on any OS.
Generate secrets and keys
Run the two key scripts, review the .env they write, then set the public, API and site URLs.
Add TLS, SMTP and storage
A reverse proxy for HTTPS, a production SMTP server (the docs recommend AWS SES), and an S3-compatible backend if you do not want files on local disk.
Start and check
sh run.sh start waits for the services to be healthy; docker compose ps shows each one.
Why is Postgres the hard part of self-hosting Supabase?
Because the other services are stateless containers you can rebuild, and Postgres is the one that holds your data. Supabase's docs put database maintenance, high availability, backups and disaster recovery on you, and the self-hosted edition has no managed backups or point-in-time recovery.
| Concern | What the docs say | Who does it when you self-host |
|---|---|---|
| High availability | Listed under "your responsibilities when self-hosting": high availability and scalability (overview) | Your team |
| Backups and PITR | Managed backups and PITR are not available when self-hosting; backups and disaster recovery are your responsibility (overview). Point-in-time recovery in Postgres means a base backup plus continuous archiving of the write-ahead log (PostgreSQL docs) | Your team |
| Major upgrades | Postgres 17 is the default; moving from 15 to 17 uses pg_upgrade through a script that needs at least twice the database size plus 5 GB free, must run as root, and drops extensions not built for 17 (timescaledb and plv8 are named) (upgrade guide) | Your team |
| Encryption key | The pgsodium root key lives in a Docker named volume; the docs say that if you lose it and have Vault secrets, they become unrecoverable, and a plain copy of the data directory does not back it up (upgrade guide) | Your team |
| Connection pooling | Supavisor is the default pooler. Pool size defaults to 20 and the client limit to 100, and its transaction mode does not support prepared statements (accessing Postgres) | Your team |
| Direct access | Postgres is reachable only through the pooler by default; exposing it for pg_dump or migrations opens the database to the network and needs firewall rules (accessing Postgres) | Your team |
| Monitoring | Advanced metrics beyond logs are not available when self-hosting; the docs point to a community-maintained observability project (overview) | Your team |
Sources linked in each row, checked 17 Nov 2026. Supabase maintains these docs; the OSStend reading is that each item needs an owner and an on-call rota.
What does self-hosted Supabase lose compared with Supabase Cloud?
Supabase lists what is missing: branching, advanced metrics beyond logs, managed backups and PITR, analytics and vector buckets, ETL and the Management API. Settings are environment variables, and support is community-based.
| Self-hosted Supabase | Supabase platform | |
|---|---|---|
| Projects | One per deployment | Plans from Free to Enterprise; Pro from $25 a month, Team from $599 (pricing, checked 17 Nov 2026) |
| Backups | Yours to build and test | Daily backups stored 7 days on Pro and 14 days on Team (pricing, checked 17 Nov 2026) |
| Branching, ETL, Management API | Not available | Platform features (overview, checked 17 Nov 2026) |
| Support | Community: Discussions, Issues, Discord, Reddit | Email support on Pro; priority email support and SLAs on Team; uptime SLAs on Enterprise (pricing, checked 17 Nov 2026) |
| Moving a project | Supabase documents restoring a platform project into a self-hosted install (restore guide) | The source project for that restore |
Sources: self-hosting overview, pricing and restore guide, checked 17 Nov 2026. Supabase's plans change; read its pricing page before you decide.
For every usage line on the platform, see Supabase pricing explained; for Supabase against Neon, Neon vs Supabase; for the platform set against a dedicated database, Supabase alternatives. For free plans across vendors, see free Postgres hosting.
Is there a split that works: Supabase's services yourself, a managed Postgres underneath?
It can, and it is the one split worth testing, but it is not something Supabase's docs describe. The pages read for this guide treat Postgres as one container of the stack, with roles and extensions the other services expect, and do not describe pointing the stack at an external database.
The Docker guide says several services need specific configuration inside Postgres, points to the default roles, and mounts the extension migration scripts into the database container at start-up (Docker guide, checked 17 Nov 2026). A database run by someone else has to provide the same roles, schemas and extensions at a version the services accept. That is a check to make on your Supabase version before you commit to the split, and it is the first item an engineer would review.
| Layer | Your team | A managed PostgreSQL service |
|---|---|---|
| Studio, gateway, Auth, Storage, Realtime, Edge Runtime | Run, patch, upgrade and monitor | Not covered |
| PostgreSQL: high availability, backups, point-in-time recovery, upgrades, pooling | Hand over | Design, run and tune, 24/7 |
| Roles, schemas and extensions the Supabase services expect | Supply the list for your version | Confirm they can be provided, then run them |
Descriptive. OSStend does not run Supabase or any of its services; it runs PostgreSQL.
OSStend is the second column for PostgreSQL only: it designs, runs and tunes dedicated community PostgreSQL in its cloud, your cloud account or your data center, with named AceMQ engineers on call 24/7. Whether a given self-hosted Supabase version can use an external database is settled in the design review, not on this page. See managed PostgreSQL and Supabase alternatives.
What does self-hosting Supabase cost to plan for?
Self-hosted Supabase is open source and Supabase publishes no price for it, so the cost is the infrastructure and the people. The lines to budget are the server at the docs' size, backup storage, TLS and SMTP, and the engineer time for monthly releases, upgrades and on-call.
| Cost line | What drives it | Where it comes from |
|---|---|---|
| Server and disk | 4 GB RAM, 2 cores and 40 GB at the minimum; 8 GB, 4 cores and 80 GB or more recommended; more if Logflare and Vector run | Docker guide, checked 17 Nov 2026 |
| Backup and restore tests | Storage for backups and WAL, plus time to prove a restore works | Overview, checked 17 Nov 2026 |
| Edge services | A TLS proxy, a production SMTP server, an S3-compatible store if not on local disk, a secrets manager | Docker guide, checked 17 Nov 2026 |
| Releases | Stable snapshots about monthly, merged with update.sh; breaking changes to read each time | Update guide, checked 17 Nov 2026 |
| On-call | Someone who can restore the database at 3 a.m. | Your own rota, or an engineering partner |
No price is shown: the figures depend on your cloud, your region and your team. To price a PostgreSQL cluster in different ways, use the managed database cost calculator.
When should you stay on Supabase Cloud?
Stay on the platform when no rule forces your data into your own infrastructure, and your team does not want to own Postgres operations. Supabase's own docs advise starting with the managed platform if you are new to Linux administration, Docker and networking.
Contact us if
- ✓Compliance or data-location rules require the stack in your own account or data center.
- ✓You want a single environment you fully control, and a team that can run Docker, a proxy and Postgres.
- ✓The database must be designed, run and on call by named engineers: see managed PostgreSQL.
Not a fit if
- ✕You need branching, managed backups with point-in-time recovery or several projects: the platform has them and the self-hosted edition does not.
- ✕Nobody on the team wants the pager for Postgres.
- ✕You are building a prototype: the Supabase free plan or Pro is simpler.
FAQ
Is self-hosted Supabase free?
The software is open source: the Supabase repository is published under the Apache 2.0 licence (GitHub, checked 17 Nov 2026). You pay for servers, storage, a mail provider and the time to run it, and Supabase lists no price for self-hosting.
Can I run self-hosted Supabase against an external Postgres?
The self-hosting pages read on 17 Nov 2026 describe a Postgres container with roles and extensions the other services expect, and do not describe an external database (Docker guide). Check your version before you design around it.
Does self-hosted Supabase include backups?
No managed backups or point-in-time recovery: Supabase lists them among the platform features that self-hosting lacks, and backups and disaster recovery are your responsibility (overview, checked 17 Nov 2026).
How do I keep self-hosted Supabase up to date?
Supabase publishes stable snapshots about once a month and an update.sh script that merges the new configuration over yours; Postgres 15 to 17 is a separate pg_upgrade procedure (Docker guide, Postgres 17 guide, checked 17 Nov 2026).
Does OSStend run self-hosted Supabase?
No. OSStend runs PostgreSQL, not Supabase or its Auth, Storage, Realtime or Edge services. It can design and run the database layer, and whether a self-hosted Supabase version can use it is checked in the design review.
Related pages
- GuideSupabase pricing explained (2026)Supabase pricing in 2026 from Supabase's published plans: Free, Pro, Team and usage lines for compute, storage, egress and auth, with worked examples.
- ComparisonNeon vs Supabase for production Postgres (2026)Neon vs Supabase compared on pricing, branching, limits and production fit, with plan prices read from both vendors' pages and when neither fits.
- AlternativeSupabase alternative for production PostgreSQLA Supabase alternative for the database layer: dedicated PostgreSQL in your cloud account or data center, run 24/7. Supabase plans checked 9 Nov 2026.
- GuideFree Postgres hosting: free tiers compared (2026)Free Postgres hosting compared: limits and catches for Aiven, Neon, Supabase, Prisma Postgres, Koyeb, Render and Railway, read on vendor pages 15 Nov 2026.
- PostgreSQLManaged PostgreSQL service and Postgres hostingManaged PostgreSQL service, compared: how to choose between RDS, Aiven, Crunchy Bridge, Neon and a tailored cluster run 24/7 in your cloud or ours.
- Tools · CostManaged database cost calculatorFree managed database cost calculator: price one cluster self-run, on a cloud database service and with managed providers, from sourced, dated list prices and your team's time.
Bring your Supabase design to an engineer
45 minutes: the stack, the database size and the recovery you need are reviewed, and an engineer says what fits where.
- ✓A design sketch for your workload, not a plan menu
- ✓A zero-downtime cutover path for what you run today
- ✓A price for that design, after the review