Here’s everything that happened with Supabase in the last month:
Custom OAuth/OIDC providers for Supabase Auth
Connect any OAuth2 or OpenID Connect identity provider to your Supabase project, including GitHub Enterprise, regional IdPs, and any standards-compliant provider, with PKCE enabled by default.
[Blog]
New tables in the public schema are no longer auto-exposed to the Data API
Starting April 28, new Supabase projects can opt out of automatic Data API exposure for public schema tables. Explicit Postgres grants are now required to make a table reachable via PostgREST or GraphQL. This becomes the default for all new projects on May 30.
[GitHub Discussion]
Supabase is now ISO 27001 certified
Supabase is certified to ISO/IEC 27001:2022, covering the information security management system across the entire platform.
[Blog]
Stripe Sync Engine moves to Stripe
The Stripe Sync Engine, originally built by Supabase, is now part of the Stripe GitHub org. It is open-source and will be maintained by Stripe going forward.
[Blog]
Supabase brand survey
Help shape the direction of Supabase. The brand survey takes a few minutes and closes soon.
[Take the survey]
@supabase/server
A new SDK that handles auth, client creation, CORS, and context injection across runtimes. Works on Edge Functions, Vercel Functions, Deno, Bun, and Cloudflare Workers.
[Blog] [Docs]
Quick Product Announcements
The Supabase app in the Stripe Marketplace is now generally available. [Stripe Marketplace]
Branching without Git is now the default. Create branches directly from the dashboard without a GitHub integration. [Blog]