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.

RLS rescue guide

Supabase RLS blocks your app queries in production

Supabase Row Level Security protects data but also blocks queries when policies are missing or wrong. The app works in development but fails in production with permission denied errors.

Supabase VPS

What is probably broken

Your app reads and writes data locally, but in production every query returns permission denied because RLS policies are too restrictive or missing.

What production should look like

Correct RLS policies that protect data while allowing your app to function, with service role keys properly secured.

STEP 01

Find the failing queries

Check your app logs and Supabase dashboard to identify which tables and queries are blocked.

Look for 403 or permission denied errors in app logs.
Check the Supabase SQL editor for policy evaluation details.
Identify which roles (anon, authenticated, service_role) the queries run under.

STEP 02

Fix the RLS policies

Write policies that allow legitimate app access while keeping data protected.

Add SELECT policies for tables the app needs to read.
Add INSERT and UPDATE policies with user ownership checks.
Test policies in the Supabase SQL editor before deploying.

STEP 03

Secure service role keys

Service role keys bypass RLS. They must never reach the browser.

Confirm service_role keys are only used server-side.
Rotate any service role key that was exposed in client code.
Use anon key for browser requests and authenticated role for user actions.

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 diagnoses and fixes Supabase RLS errors during production deploy so your app can read and write data correctly.

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

Deploy my app

Related guides