Skip to content
Switching

When you need the app next to the database

Supabase is an excellent Postgres platform. Veltic is a different trade: it also runs your Node application and your long-lived workers in the same project.

Shared
PostgreSQL
Both are stock Postgres with row level security.
Different
Compute
Veltic runs full Node applications and persistent workers.
Missing
End-user auth
Veltic has no built-in end-user authentication product.
  • What carries over unchanged

    Your schema, your migrations, your row level security policies and your SQL. Both platforms run real PostgreSQL.

  • What Veltic adds

    Long-running Node applications and background workers as first-class resources, deployed and monitored in the same project as the database.

  • What Veltic does not have

    There is no built-in end-user authentication product and no client SDK equivalent to supabase-js. If those are load-bearing for you, that is a real cost of switching.

  • Edge Functions versus Functions

    Supabase Edge Functions are request-scoped and run on Deno. Veltic Functions are persistent Node processes. Code does not port directly; the design does.

  • Storage maps closely

    Private objects with signed transfer tickets and public objects with stable URLs. The concepts match even though the API surface differs.

  • Realtime maps closely

    Project-scoped channels with broadcast and presence, connected through a short-lived signed ticket.

Do the migration in the order that fails cheaply

Move the schema first and verify it with a restore. Then move background jobs, because they are the least user-visible. Move the application next. Leave anything that depends on end-user auth for last, since that is where you will need to write new code rather than move existing code.

The deciding question

If you need integrated end-user authentication and the Supabase client SDK, stay. If you want a database, a full Node application and long-running workers operated together, Veltic is the better shape.

Build the whole backend in one project

One plan, one dashboard, one command line interface. PostgreSQL, applications, functions, storage and realtime.