DeployVera PaaS · Supabase migration

Moving from Supabase to DeployVera

Supabase is not one product but a bundle: Postgres, Auth, Storage, Realtime and Edge Functions. DeployVera does not replace all of them; it offers the Docker runtime for your app and a managed PostgreSQL (beta). This guide separates what you can move from what is better left on Supabase.

Last reviewed:

What you can move to DeployVera

  • The application itself: API, web app or worker, with a Dockerfile or automatic build.
  • A database you use as plain Postgres: schema and data via pg_dump / pg_restore or psql.
  • Environment variables, domain and HTTPS.

What DeployVera does not replace

  • Supabase Auth (user sessions, providers): there is no equivalent on DeployVera.
  • Supabase Storage: there is no file storage service; objects on Supabase must be moved separately.
  • Realtime and Edge Functions: no equivalent.
  • The database is beta; backups are platform-level with no self-service download or restore.

Two paths: which one?

For most projects the lowest-risk path is to move only the app and keep using Supabase as it is.

SituationSuggested pathWhy
You use Auth, Storage or RealtimeApp on DeployVera, Supabase stays as isThese services have no equivalent on DeployVera. The app keeps connecting to Supabase at its own address.
You use Supabase only as plain PostgresMove the app and the database to DeployVeraAll data can be moved with pg_dump; app and database run on the same private network.
Your row level security (RLS) policies use auth.uid()Do not move the databaseThose policies depend on the Supabase Auth schema and will not work without it.

Migration steps

Steps 1–3 apply to both paths. Steps 4–7 are only needed if you also move the Postgres data.

  1. 1.Make the app deployable with Docker

    Make sure it runs with its production command and listens on 0.0.0.0 on the port from the PORT environment variable. Add a Dockerfile or use a supported automatic build method.

  2. 2.Connect the GitHub repository and deploy

    In the panel choose the repository and branch, enter the port, define environment variables (including your Supabase URL and keys; keep them out of the repository) and watch the build logs. If you use Auth, Storage or Realtime you can stop here: the app runs on DeployVera and Supabase stays as it is.

  3. 3.If you move Postgres too, stop writes first

    Data must not change while you dump it. Plan a maintenance window and keep the old app read-only or off. Do not delete the Supabase project until the move is verified.

  4. 4.Dump the database from Supabase

    Use Supabase’s direct connection string; if your network lacks IPv6 you can use Supabase’s session pooler string. To take only your own schema, leave out Supabase-owned schemas such as auth and storage.

    pg_dump "$SUPABASE_DB_URL" \
      --format=custom --no-owner --no-privileges \
      --schema=public --file=app.dump
  5. 5.Create PostgreSQL on DeployVera

    On the panel’s Databases page create PostgreSQL (beta) on the service your app is attached to. Get the database’s private endpoint and credentials from the panel. The public installation allows 3 managed databases per service; the limit the panel shows is authoritative.

  6. 6.Import the dump

    Do not assume the private endpoint is reachable from the internet. If you have a direct network path use pg_restore; otherwise open a support ticket and ask for an operator-assisted import (the Migration package covers one database). A plain SQL dump, such as Supabase’s dashboard backup, can also be loaded with psql -f. Supabase-specific extensions do not come along automatically; confirm with support which ones are available.

    pg_restore --no-owner --no-privileges \
      --dbname "$DATABASE_URL" app.dump
  7. 7.Switch DATABASE_URL and verify

    Replace DATABASE_URL in the application’s runtime environment with the DeployVera database and redeploy. Compare row counts, critical queries and application logs with the old database. Keep the Supabase project until everything is verified.

What to know

  • Supabase’s dashboard backup contains CREATE commands for all schemas, so “already exists” errors are expected when loading into a new project. Edge Functions, Auth settings, Realtime settings, extensions and read replicas are not carried by that backup; for Storage only file metadata is in the backup and the objects themselves must be moved separately.
  • Database backups on DeployVera are platform-level; the customer panel currently has no per-database self-service backup download or one-click restore. Set an independent backup policy for critical data.
  • pg_dump and pg_restore are standard PostgreSQL tools; adapt the options to your schema.

Sources

Frequently asked questions about moving from Supabase

Does DeployVera replace Supabase?

No. Supabase is a bundle of Postgres, Auth, Storage, Realtime and Edge Functions. DeployVera offers an application runtime and managed PostgreSQL (beta). You can keep using Supabase for Auth, Storage and Realtime.

Can I move the app to DeployVera and leave Supabase as is?

Yes. Your app connects to Supabase at its own address; define the Supabase URL and keys as environment variables. You do not have to move the database.

How do I move the Postgres data?

Take a dump from Supabase with pg_dump and load it into the PostgreSQL you create on DeployVera with pg_restore. Because the private endpoint may not be reachable from the internet, the import often happens with support.

Do my Supabase Auth users move?

No. User sessions and the Auth schema are not moved to DeployVera. If you use Auth, keep Supabase for it.

Is there an SLA for the database?

No. PostgreSQL is in beta and no SLA is offered.

Try the app on the free plan first.

Publish the app on DeployVera without touching Supabase; decide about the database later.

Create a free account