What do I need to set up Supabase on a VPS?

You need a VPS (starting at $4-6/month), SSH access, and the app code in a GitHub repo. For Supabase and VPS, you also need environment variables, a domain, and SSL configured before going live.

How long does it take to move to a VPS?

A straightforward Supabase deployment takes 2-4 hours for someone familiar with servers. RepoAssistant does it in 24h with a ship-or-refund guarantee.

How much does it cost to host Supabase on a VPS?

A VPS for Supabase or VPS starts at $4-6/month for a 1-2 GB instance from providers like Hetzner, DigitalOcean, or Hostinger. RepoAssistant's deploy service is a fixed $39-149 one-time fee.

What if something breaks after deployment?

Every deployment includes a smoke test (login, forms, database writes, API calls) and a handover doc with restart, rollback, and deploy commands. If the app is blocked pre-launch, we fix and ship within 24h or refund.

Self-host checklist

Self-host Supabase on a VPS without losing your data

Supabase self-hosting gives you full data control and predictable cost. But you own the server, the database, the backups, and the recovery plan.

Supabase VPS

What is probably broken

Managed Supabase is convenient but you want data ownership, predictable cost, or to run everything on one VPS.

What production should look like

A self-hosted Supabase instance with persistent volumes, automated backups, and a tested restore path.

STEP 01

Plan the self-host setup

Self-hosting is a commitment. Make sure you are ready before starting.

Choose a VPS with enough RAM and disk for Postgres and Supabase services.
Plan your backup strategy before creating any data.
Decide whether you need all Supabase services or just Postgres and auth.

STEP 02

Deploy with Docker Compose

Supabase self-hosts as a Docker Compose stack with multiple services.

Use the official Supabase self-host Docker Compose file.
Configure named volumes for Postgres and storage data.
Set secrets in the server environment, not in the compose file.

STEP 03

Back up, test restore, and connect apps

A backup you have not tested is not a backup.

Set up automated Postgres backups to a separate location.
Run a restore test before treating the server as production.
Point your app DATABASE_URL and Supabase env vars at the self-hosted instance.

Quick check

Is your app production-ready?

If you cannot tick all five, we can fix it. Send us the repo and we handle the rest.

?Custom domain with HTTPS
?Environment variables configured
?Database wired and backed up
?Auto-deploy on push
?Smoke tested and live

Free checklist

Deploying this yourself?

Get the exact 5-step checklist we run before every deploy. No fluff, just the things that actually break.

Done-for-you deploy

RepoAssistant sets up self-hosted Supabase with backups, restore testing, and app connectivity checked.

Fixed price per repo. 24h delivery or full refund. No hourly billing.

Deploy my app

Related guides