Supabase compatibility

Each Plurabase project runs its own copy of Supabase's open-source services, pinned to the images of Supabase's self-hosted release self-hosted/v0.8.2 (commit 564eab8), except Studio, which is built from Supabase's source with Plurabase changes. Compatibility therefore means compatibility with self-hosted Supabase at those versions, exercised in a private lab with @supabase/supabase-js v2. It does not mean parity with Supabase Cloud. Statuses use the words defined on the facts page.

Database and REST#

Status: Available in pilot (database.postgres)

Status: Available in pilot (database.rest)

Tables, views, foreign keys, enums, functions and triggers work as in PostgreSQL 17.6. PostgREST serves CRUD and RPC; Row Level Security applies to requests made with the publishable key and user JWTs. Direct PostgreSQL connections from outside the host are not offered. Keep the graphql and graphql_public schemas: PostgREST needs them at start-up.

Studio#

Status: Available in pilot (database.studio)

Owners and admins of a project open its Supabase Studio (Table Editor, SQL Editor, Auth, Storage, Functions) from the Plurabase console. The Studio gate requires the pilot's Tailscale identity, a console session and a Studio grant for that session, and adds Studio's HTTP Basic credential itself. On the pilot host owners and admins can also reveal that credential in the console, and it is long-lived; key rotation, written and not deployed, stops revealing it and rotates it with the project's keys (see key rotation). Studio acts with administrative authority: its SQL bypasses RLS. Test your policies with user tokens, not from Studio.

Auth for your application's users#

Status: Available in pilot (auth.email-password)

Status: Planned (auth.providers)

Email and password sign-up, sign-in, token refresh and sign-out work with GoTrue. Confirmation and recovery emails for your users go to a mail catcher on the pilot host and are not delivered outside it. OAuth providers, custom SMTP, phone OTP and SAML SSO are not configured. Plurabase's own sign-up for platform accounts is a separate system, described under security.

Storage#

Status: Available in pilot (storage.buckets)

Private and public buckets, path-based RLS policies, upload, download and expiring signed URLs work through supabase-js. The S3 protocol, resumable uploads and image transformations have not been verified.

Realtime#

Status: Available in pilot (realtime.changes)

Postgres Changes are delivered over WebSocket for tables added to the supabase_realtime publication. Broadcast and Presence have not been verified.

Edge Functions#

Status: Available in pilot (functions.edge)

Functions use Deno.serve, run on the pilot host and can read encrypted per-project secrets. A function may import its own local files and pinned versions of @supabase/supabase-js v2 and @supabase/server; remote npm and jsr imports are not downloaded. A deploy names the revision it replaces, so two deploys cannot overwrite each other silently. There is no global edge network.

Shared plan projects#

Status: In development (projects.shared)

A shared plan project runs its own database, Auth and REST services on a host shared with other projects and uses that host's Realtime and Storage services. Studio, Edge Functions in one microVM per project, function logs, image transformations and database webhooks exist as code for these projects; none of it has run on a host. Three things are not offered on a shared project, and their requests get a 409 that states why:

• Postgres, API and Auth logs: no log pipeline collects them for shared projects yet.
• The S3 protocol: shared Storage issues no S3 access keys.
• Resumable (TUS) uploads: shared Storage accepts only bucket and object requests, so files go through the standard upload, up to 16 MiB.

Not available#

Status: Planned (database.branching)

Status: In development (database.pitr)

Branching, read replicas, point-in-time recovery, log drains, the Supabase Management API and the Supabase CLI are not available. Point-in-time recovery is written (WAL archiving, ADR-0031) but not enabled on the pilot host. For the full list see the facts page.