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

You need a VPS (starting at $4-6/month), SSH access, and the app code in a GitHub repo. For Cursor and Supabase, 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 Cursor 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 Cursor on a VPS?

A VPS for Cursor or Supabase 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.

Supabase connection rescue

Cursor app loses Supabase connection after moving to production

Cursor apps connect to Supabase using local env vars. After deploy, the server cannot reach the database until URLs, keys, and network rules are configured.

Cursor Domain Supabase VPS

What is probably broken

The app loaded data in Cursor dev mode. After deploy, every database call fails with connection refused or authentication errors.

What production should look like

The Cursor app connecting to Supabase from your production server with correct URLs, keys, and network access.

STEP 01

Find the Supabase credentials

Locate the project URL, anon key, and any service role key the app uses.

Check the Supabase dashboard for project URL and keys.
Search the Cursor workspace for Supabase initialization calls.
Identify whether the app uses a direct connection or a pooled connection string.

STEP 02

Configure server network access

The server must be able to reach Supabase endpoints without firewall blocks.

Confirm the VPS can reach the Supabase host on the required ports.
Check Supabase IP allow lists if you have network restrictions enabled.
Verify DNS resolution from the server resolves Supabase hosts correctly.

STEP 03

Wire the app and test

Set the credentials on the server, rebuild, and test every data flow.

Add Supabase URL and key as server environment variables.
Rebuild the app and confirm it connects to the database.
Test reads, writes, auth, and any storage or realtime features.

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 wires Cursor apps to Supabase in production with correct credentials, network config, and smoke tests.

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

Deploy my app

Related guides