LoginSign Up
← Back to all sparks
Supabase logo

Supabase

INFRA · APISDEVOPS
Velocity0.0

Open-source Firebase alternative with PostgreSQL

supabase.com ↗

Supabase is closing its most-exploited default: tables stop being public unless you say so.

secure-defaultsbreaking-changesrow-level-securitypostgrestauth
◆Current state
The last month is dominated by tightening defaults rather than adding surface. New tables in the public schema will no longer be auto-exposed to the Data and GraphQL APIs, pg_graphql stops being enabled by default, and the OAuth token endpoint is being corrected to return 200 per OAuth 2.1. Alongside that, custom OAuth/OIDC providers landed for Auth and an RLS Tester entered preview.
◆Where it's heading
Supabase is paying down the security cost of its own convenience. Auto-exposing every public-schema table made the product fast to start with and easy to misconfigure; the fix is explicit Postgres grants, staged over six months from new projects in April to all existing projects on October 30. The RLS Tester is the same theme from the other side — the auto-exposure default only worked if row-level security was correct, and until now there was no way to check.
◆Prediction
Expect the remaining rollout dates to hold and more of the developer experience to be rebuilt around explicit grants, with the RLS Tester graduating from preview as it becomes the tool people need to verify the new model. The October cutover for existing projects is the moment where this stops being an announcement and starts breaking things.

◆Recent moves

  1. 3mo ago

    Deprecation Notice: Dropping Support for Node.js 20

    supabase-js drops Node.js 20 support, forcing an upgrade for SDK users still on it. Routine runtime maintenance, but it lands in the same window as several other changes that require action.

    View source ↗
  2. 3mo ago

    Developer Update - May 2026

    The monthly roll-up, led by custom OAuth/OIDC providers for Auth and the end of automatic Data API exposure for public-schema tables. It reads as a summary of the security-defaults push rather than a set of new capabilities.

    View source ↗
  3. 3mo ago

    Breaking Change: OAuth token endpoint will return HTTP 200 instead of 201

    The OAuth token endpoint moves from 201 to 200 on May 26 to comply with OAuth 2.1, which had been breaking strict clients. Only integrations explicitly checking for 201 are affected — the widely used SDKs test for any 2XX.

    View source ↗
  4. 3mo ago

    Breaking Change: Tables not exposed to Data and GraphQL API automatically

    ⚡ SPARK

    The change that defines this window: tables in the public schema stop reaching the Data and GraphQL APIs unless explicitly granted. It reverses the default that made Supabase quick to start with and easy to leak from, on a staged timeline ending with all existing projects in October.

    View source ↗
  5. 3mo ago

    Fragment of the no-auto-expose announcement

    A partial capture of the same auto-exposure announcement, containing only its timeline section. It duplicates the canonical entry.

    View source ↗
  6. 3mo ago

    Feature Preview: RLS Tester

    A preview UI for testing row-level security policies via role impersonation, showing which policies a query evaluates. It answers a long-standing gap raised in GitHub discussions, and it matters more now that explicit grants and RLS are the only things standing between a table and the API.

    View source ↗