In a forthcoming release within approximately 3 weeks, pg_graphql will be disabled by default on new Supabase projects.
This change aligns pg_graphql with our security-first approach of minimizing exposed API surface area by default. Services and extensions that expose schema metadata are now opt-in rather than opt-out, reducing the default attack surface for new projects.
Who is affected:
New projects will no longer have pg_graphql enabled automatically
Existing projects older than 30 days with zero graphql requests will also have the extension disabled (where previously it was enabled by default). Existing projects with requests will be unaffected.
Action required: If your application relies on GraphQL, you can enable pg_graphql manually via the Database Extensions page in your dashboard. You can also add create extension pg_graphql to your migrations as well if you wish to keep using pg_graphql
We continue to fully support pg_graphql for projects that need it. This change simply ensures it's an intentional choice rather than a default.
We'll follow up on this thread with links to relevant documents for actions required.