Deploy self-hosted Supabase Postgres in 60 seconds (managed updates & backups)
The Postgres database at the core of Supabase — Firebase alternative building block.
Price comparison
Managed SaaS / Elestio$24 – $60 / month
Self-hosted via Railyard$22/mo Launch plan for all your apps + €5.99/mo Hetzner server
You save up to 53%
Pre-configured stack
- supabase-postgres
- Automatic HTTPS
- Daily S3 backup
Sign in with GitHub, start your 14-day trial and deploy Supabase Postgres to your own server · use email instead
What you get
- Runs from the official image supabase/postgres:15.8.1.060
- A community template, not yet verified end to end by the Railyard team
- Automatic HTTPS and zero-downtime deploys
How to deploy Supabase Postgres
- 1
Connect a server
Attach a DigitalOcean, Hetzner or Vultr server to Railyard, or any Linux box over SSH.
- 2
Click "Deploy Supabase Postgres"
Railyard builds the container.
- 3
Set your domain
Point your domain at the app. Railyard issues an HTTPS certificate and keeps it renewed automatically.
Why deploy on Railyard
Railyard runs it standalone on a server you already pay for — no addons to provision, with zero-downtime deploys and scaling still included.
Deploying Supabase Postgres is one piece of a bigger stack you can keep building — add a database, a worker, a cache, or another app, all on the same servers you already pay for.
Good for
- Just the Postgres database underneath a Supabase-style stack
- A pgvector-ready Postgres for apps that only need the database, not Auth/Storage/Realtime
Good to know
- Nothing to configure after deploy — this is only the database image, not the full Supabase stack
- Deploy the Supabase (self-hosted, core) stack template instead if you also need Auth, Storage and Studio