Skip to content
Vulcbase

Documentation

Build on Vulcbase

Vulcbase gives each project a Postgres 17 database and the services around it. If you know supabase-js, you already know the client side.

Where to start

QuickstartCreate a project and make your first query in five minutes.Migrate from SupabaseWhat the importer copies, what it does not, and how to switch.Database and RESTPostgres access, the REST API, RPC, extensions and policies.AuthEmail and password, magic links, codes, anonymous users and PKCE.StorageBuckets, policies, signed URLs and image resizing.RealtimeDatabase changes, broadcast and presence.Self-hostingRun Vulcbase yourself with Docker Compose.Plan limitsProjects, database size, storage, users and backups per plan.

How it works

Each project has its own Postgres database and its own URL. Requests to that URL go through the Vulcbase gateway, which serves four APIs on one address:

  • /rest/v1 for tables, views and functions (the PostgREST-style API that supabase-js uses).
  • /auth/v1 for users and sessions.
  • /storage/v1 for buckets and files.
  • /realtime/v1 for database changes, broadcast and presence.

The same project can be reached directly over the Postgres protocol with the connection string from the project settings. Row Level Security is what decides what each request can read and write, exactly as in Supabase.

URL and keys

A project has a project URL and two API keys: the anon key, safe to ship in browsers and mobile apps, and the service_role key, which bypasses Row Level Security and belongs only on your server. Both are signed with the project's own JWT secret, which you can rotate from the project settings.