Switch from Neon or any Postgres
Your Postgres, plus everything around it.
Move a Neon, RDS or self-hosted database with pg_dump and psql, record it as your first migration, and get auth, storage, functions, realtime and rules on top.
What you gain
Four steps
- 1
Check extensions
Compare what you use with what Sovaria offers and turn those on first.
select extname, extversion from pg_extension order by 1; - 2
Dump
The public schema, without owners or grants (Sovaria manages roles).
pg_dump "$OLD_DATABASE_URL" --schema=public --no-owner --no-privileges --format=plain --file=dump.sql - 3
Restore
All or nothing, stopping at the first error.
psql "postgresql://USER:PASSWORD@db.ORG.sovarias.in:5432/DB?sslmode=require" \ --set ON_ERROR_STOP=1 --single-transaction --file=dump.sql - 4
Record a baseline
So staging and production stay in step from here on.
sov link sov db pull
Everything has a place
Neon or PostgresSovaria
DatabasePostgres 16 per project, dedicated on higher plans
BranchesEnvironments with their own URL and data
Roles and grantsManaged by Sovaria; app access goes through RLS and policies
pg_cronFunction schedules
LISTEN/NOTIFY consumersDatabase change events and function triggers
Your API serverREST and GraphQL from the schema, or functions
Questions
Which Postgres version?
Sovaria runs PostgreSQL 16. A version 16 pg_dump reads older servers.
What about my roles and grants?
They don’t move: Sovaria manages database roles. Policies written for roles Sovaria doesn’t have are rewritten as TO public with a condition on the signed-in user.
Read more
Start building on Sovaria
A free project takes a minute. Your data stays behind rules from the first request.