We are happy to announce that we are rolling out the cached egress changes for everyone as previously announced in the last launch week.

Cached and uncached egress will have independent quotas and independent pricing. Cached egress is egress that is served from our CDN via cache hits, whereas uncached egress is egress against the origin (your Supabase project).

You are getting more quota in all cases and cached egress is getting 3x cheaper. Especially for heavy storage users that were previously serving files via our Smart CDN, this should come with a hefty discount.

You can see your current storage usage and daily storage usage on your organization's usage page:

Other useful insights:

• "Storage Top Cache Misses" under project logs templates
• "Storage Egress Requests" under project logs templates

If you are not yet seeing the cached egress metrics on your organization's usage page, then your plan is scheduled to change with the next billing cycle reset and you should start seeing it after. If you have higher storage egress costs and you don't see any of the metrics yet, please reach out to support, to expedite.

For more information about egress billing, refer to our docs.

Hey Supabase community! 👋

We're excited to share that we're adding OAuth 2.1 server capabilities to Supabase Auth, turning your Supabase project into a full OAuth authorization server. This means your project can act as an identity provider for third-party applications, similar to how you might use "Sign in with Google" today.

Current Status: Alpha prototype in development

Target Date:

• Generally available: Q4 2025
• Early access release / beta: Mid-September 2025

What We're Building#

We're implementing OAuth 2.1 authorization server capabilities that will allow your Supabase project to:

• Act as an identity provider for third-party applications
• Enable "Login with [Your App]" functionality
• Eventually support OpenID Connect (OIDC) for full SSO capabilities

Exciting Use Cases#

MCP (Model Context Protocol) Auth#

Use your Supabase project as the auth provider for AI agents and LLM tools that support MCP.

"Login with Supabase Project"#

Enable third-party applications to offer "Sign in with [Your App]" - turning your Supabase project into an identity provider like Google or GitHub.

Enterprise SSO (via OIDC - coming next)#

Act as a single sign-on provider for your organization's internal tools.

API Access for Partner Integrations#

Securely grant scoped access to your API for third-party developers and partners.

How It Works#

Here's the authorization flow we're implementing:

Key Design Decision: Flexible Authorization UI#

Traditional OAuth servers host your application's UI. Instead, we're giving you complete control over the authorization and consent screens. After the initial /authorize call the user is taken to your app's frontend to be presented with the consent screen. This provides the freedom to build your app how you want, while Supabase Auth takes care of the protocol specifics:

• Design custom login/registration flows (can use your existing login as it is)
• Implement your own consent screens
• Handle authentication however you prefer (password, social login, MFA, etc.)

This gives you maximum flexibility to match your application's design and user experience.

What Supabase Provides#

• OAuth 2.1 Protocol Handling: Full implementation of authorization code flow with PKCE
• Token Management: JWT access tokens and refresh tokens
• Client Registration:
  • Dashboard UI for manual client registration
  • Dynamic client registration API (perfect for MCP auth!)
• Token Validation: JWKS endpoint for third-party token validation, thanks to asymmetric JWTs
• APIs for Authorization Flow: Endpoints to handle approval/denial decisions
• Client Libraries: SDK updates for easy integration (coming soon)
• UI Components: Consent screen components via Supabase ui.supabase.com (planned)

What You Need to Implement#

• Authorization/Consent UI: Create your own login and consent screens
• User Authentication Logic: Handle how users prove their identity
• Consent Management: Present scope information (tbd) and capture user approval

Access Token Structure#

Access tokens will be JWTs (like current Supabase tokens) with:

• All standard Supabase claims (user_id, role, etc.)
• Additional client_id claim for OAuth client identification
• Compatible with existing Row Level Security(RLS) policies (same role claim structure)

Balancing RLS Power with OAuth Scopes#

We want to preserve the power and flexibility of RLS policies while also enabling developers to "scope down" access tokens based on OAuth scopes. This is a challenging balance - RLS gives you fine-grained, row-level control, while OAuth scopes traditionally work at a higher level.

Our current thinking includes exploring these approaches:

1. Custom Access Token Hook: Extend the existing hook system to modify token claims based on OAuth context
2. OAuth-specific Access Token Hook: A new dedicated hook that runs only for OAuth token generation
3. JWT Template System: Define templates that control token structure based on client/scope combinations

Initial Limitations & Future Roadmap#

Phase 1:

• Authorization code flow with PKCE
• Refresh tokens
• No scope management initially (tokens have full user privileges, rely on RLS for authorization)

Phase 2:

• OpenID Connect support
• Scope management system & customization of tokens generated by OAuth flows

We Need Your Feedback!#

We'd love to hear your thoughts on:

1. Scope Management & Token Customization#

Currently, we're starting without a scope system: OAuth tokens will work like regular session tokens with full user privileges. Authorization happens via RLS policies. We're exploring ways to "scope down" OAuth tokens while preserving RLS:

• Would you prefer Custom Access Token Hooks, OAuth-specific hooks, or JWT templates?
• How should OAuth scopes translate to token restrictions?
• Would you need granular scopes immediately or is basic token customization enough to start?

2. OpenID Connect Features#

As we plan OIDC support, which features are most critical for you?

• Userinfo endpoint
• ID tokens
• Specific claims in ID tokens
• Session management
• Other OIDC features?

3. Dashboard UI for OAuth Client Management#

What would you need in the dashboard?

• Client registration and management
• Consent history and revocation
• Token analytics
• Scope configuration (when available)
• Testing tools?

4. Your Use Cases#

What would you build with this? We're especially interested in:

• Use cases we haven't considered
• Integration scenarios with existing systems
• Security or compliance requirements
• Performance or scaling considerations

Questions?#

Drop your questions, feedback, and use cases below! We're actively working on this and your input will directly influence the implementation.

We've fully rolled out the Deno 2.1 compatible release on all regions serving Edge Functions. You don't need to change your existing Edge Function invocations; the nearest region will automatically serve them using the Deno 2.1 release.

Along with the Deno 2.1 release, the features we announced during the launch week also became available in all regions: https://supabase.com/blog/persistent-storage-for-faster-edge-functions

Fallback to Deno 1.45#

In case your Functions start experiencing any compatibility issues with Deno 2.1, you can temporarily fallback to the 1.45 release in two ways:

• Add query parameter forceDenoVersion=1 to your function requests

• Add x-deno-version: 1 header in requests

If you have any issues and questions about this update, please create a support request

What changed#

Using realtime-js library in Node.js < 22 will require to set transport for Realtime

What do I need to do#

For most users (Browser, Node.js 22+): No changes required For Node.js < 22 users: You’ll need to make a small change to explicitly set the WebSocket transport (see line 9 below).

[!WARNING]
We are working on a fix for the type definition as currently it's not being accepted as a WebSocketLike interface.

Why did we change it#

We have been facing multiple issues where the dynamic import of ws was breaking several runtimes and environments. The first environment where this become a serious issue was with Expo which required us to tackle the issue.

Previous attempts#

Multiple NPM entrypoints#

PR: https://github.com/supabase/realtime-js/pull/476

First approach chosen in conjunction with the Expo team but ended up creating several issues in other runtimes (namely Deno and Browser) so we reverted to use another method

Polymorphic client#

PR: https://github.com/supabase/realtime-js/pull/485

Second approach chosen as it's usually the "default" as we accepted the overhead of having a polymorphic WS connector but this created issues with Vercel ( https://github.com/supabase/supabase-js/issues/1437 )

Current approach#

After our several attempts in handling how Javascript runtimes handle dynamic imports we had to change the way we support Node.js < 22 as it was the original source of the issue due to the lack of native WebSocket support

The changes are implemented in realtime-js@2.15.1 with the changes from https://github.com/supabase/realtime-js/pull/514 The changes are implemented in supabase-js@2.55.0 with the changes from https://github.com/supabase/supabase-js/pull/1529

We opted to use this approach as it fully prevents the usage of dynamic imports; it avoids external library issues; has a path for upgradability and avoids multiple entrypoints which proven to be error prone.

As part of the restructuring of the python environments, both the gotrue and supafunc python packages are being deprecated, in favor of supabase_auth and supabase_functions respectively.

gotrue 2.12.4 and supafunc 0.10.2 have both been published with no changes other than metadata changes, and including deprecation warnings when importing from them.

[!WARNING] Please note that 2.12.3 is the last version where both gotrue and supabase_auth are the same, and they will diverge going forward. The same is valid for supafunc and supabase_functions version 0.10.1.

Affected libraries#

• supabase-py
• gotrue
• supafunc

Timeline#

Package name changes: December 14, 2024 Deprecation Notice Issued: August 8, 2025

Why?#

This name change has occurred in December 2024, in trying to keep name parity with the JavaScript libraries, but these old packages have been receiving the same updates through a script in the publishing workflow. As part of the python CI restructuring effort, it doesn't make sense to keep two versions of the same package around, and thus they're not going to receive patches anymore.

What You Need to Do#

Change all package references from gotrue to supabase_auth, and supafunc to supabase_functions, in pyproject.toml, setup.py, or other package metadata formats, and change all direct imports from those libraries (from gotrue import ...) to importing from the new ones instead (from supabase_auth import ...).

supabase-py 2.18.1 will drop all usages of gotrue and supafunc from the main library. If you are using gotrue and supafunc directly as transitive dependencies, please prefer importing directly from supabase instead (see this comment for more info).

[!WARNING] This is not going to be available for long, as feature differences are bound to occur sooner or later.

Thank you for your attention and continued support. If you have any questions, feel free to reach out through GitHub Discussions or our community channels.

As part of our ongoing efforts to make Dashboard easier to use, we’re moving service-related settings in their respective areas. Take database settings, for example:

• Previously: you had to go to Project Settings → Database to make database-related configuration changes.
• Now: Any database-related configuration can be found in Database → Configuration.

Project-level settings like Data API will remain in Project Settings.

Before	After
Before: No database settings to be found!	After: Database settings along with access control in one simple section.

Pretty simple. But, because we’re changing routes, this might confuse folks expecting to find things where they used to be.

Here’s how we’re making this change as smooth as possible:

• Redirects have been added so the old URLs will keep on working.
• References in documentation have been updated.
• The old navigation (e.g. Project Settings → Storage) will stick around for a few months. They’ll just be treated as shortcuts to their new homes.

What’s affected#

The full list of affected services and/or settings include:

• Database
• Data API
• Authentication
• Storage
• Edge Functions
• Log Drains

Previously	Now	Later
Previously: service-level settings scattered throughout Project Settings and their own areas.	Now: all moved out to their respective areas, but shortcuts remain here in Project Settings.	Later: we’ll remove these shortcuts to make Project Settings less noisy.

Code changes#

See #37580 for the Now changes (later today) and #37612 for the Later changes (scheduled for a few months from now).

What’s next#

Some of our settings aren’t so neat, bridging multiple services or arguably children of existing setting sections. Examples include Data API and Log Drains. We’re looking into how to better categorise them over time, which may mean more navigation changes. We’ll let you know if those happen.

Feedback#

As always, please let us know what you think or if you run into issues, here on the discussion. Thanks!

Version 17.4.1.062 of supabase was withdrawn.

"Withdrawn" means a problem was found with the image, and so it is set to "withdrawn" to prevent it's continued use for new projects.

An update will be released to our production servers ASAP. Customers are encouraged to update to this version as soon as you can after it becomes available.

However, a few customers may have created projects with it while it was released.

If so, you may see a status like this

Your options are:

1. Drop the existing project you created if it is new enough. Then, create a new which would come up under an earlier release number, and wait for update
2. Or, keep the existing project for now, and wait for update.

Once the update is available, you'll see a prompt to upgrade in the https://supabase.com/project/_/settings/infrastructure tab

Combined View for Logs#

In the upcoming days, we'll be releasing a new interface on the dashboard for logs with a unified view across all your services, along with improved filtering and real-time updates! You no longer need to find a specific collection that you'd want to look for logs from, and can now conveniently query through a single interface, which will also provide a better top-level view of your project 🙂

This is very much a heavy work in progress, but we'd be keen to hear your thoughts on what you love, what's missing, and anything at the top of your mind! Sign up here for early access to give it a try!

What we'd like to know from you#

• Any bugs or issues that you might have run into while using the new UI
• Any ideas or suggestions that you reckon will improve the DX based on how find logs
• Feel free to leave any feedback in this thread too!

As part of our ongoing commitment to providing a secure and reliable experience for all developers, we will drop support for Node.js 18 in accordance with our Support Policy.

Affected libraries#

• supabase-js
• auth-js
• realtime-js
• functions-js
• storage-js
• postgrest-js

Timeline#

Deprecation Notice Issued: July 16, 2025 End of Support for Node.js 18: October 31, 2025

Why?#

Node.js 18 reached its official end of life on April 30, 2025 and no longer receives security updates or critical fixes. Continuing to support unsupported runtimes introduces risks for both developers and end users.

What You Need to Do#

Please upgrade to a supported Node.js version (20 or later) before October 31, 2025 to ensure continued compatibility with future releases of our libraries.

Thank you for your attention and continued support. If you have any questions, feel free to reach out through GitHub Discussions or our community channels.

Overview#

We're going to roll out a Realtime Settings screen that will allow you to setup parameters for your Realtime account.

Usage#

In the Realtime section of the Dashboard, under Settings, you will find the settings you can change.

Currently we're giving you control over:

• Channel restrictions - Control wether you allow public access to your channels. Public access means that you can use Private and Public channels. As a reminder, Private channels are the ones to which you have setup Realtime Authorization.
• Database connection pool size - The amount of connections allocated to Realtime Authorization RLS checking. This will impact your join rate by being able to increase the rate of checks for your private channels. Be aware this will consume more direct connections from your database available connections
• Max concurrent clients - If you have disabled the spending cap you are able to increase the number of concurrent clients and change your Rate Limit for this specific flag.

Edge Functions are executed in the region closest to the user making the request. This helps to reduce network latency and provide faster responses to the user.

However, if your Function performs many database or storage operations, invoking the Function in the same region as your database may provide better performance. Some situations where this might be helpful include:

• Bulk adding and editing records in your database
• Uploading files

Previously, the region could only be set via the x-region header in the request. However, in some instances (e.g., CORS requests, Webhooks), the headers set in the request cannot be controlled. Considering these limitations, we've also made it possible to set the region via the forceFunctionRegion query parameter.

Please check the Regional Invocations guide for more details.

A couple of months ago, we started migrating our Edge Functions platform to use Deno 2.1. Deno 2 bridges the gap between Node and Deno by supporting Node's built-in APIs, npm modules, and package.json. This would make it easy to migrate existing Node apps to run in the Edge Functions platform.

Previously, we announced that you can start testing Deno 2.1 locally for your Edge Functions. Thanks to everyone who tried and gave us feedback.

Today, we give you the option to preview Deno 2.1 on our hosted platform. You should try running your existing Edge Functions with Deno 2.1 and report any bugs/issues.

You can first run deno lint locally on your Edge Functions code with no-deprecated-deno-api rule to find any breaking changes in Deno 2.

Once you have updated your functions, you can test them in our hosted platform as follows:

How to test for Deno 2 compatibility#

There are two ways to force your functions to run on the Deno 2 preview cluster.

• Add query parameter forceDenoVersion=2 to your function requests

• Add x-deno-version: 2 header in requests

Note: Deno 2 Preview cluster traffic will be served from us-east-2 region. You don't need to set the region explicitly.

Also, in the next couple of days, we will notify projects currently using deprecated APIs via email to update their functions to use Deno 2.

When are we fully rolling out Deno 2.1?#

Based on the feedback and issues we discover in this preview, we will decide the timeline on making Deno 2.1 the default runtime in our hosted platform. Current ETA is within 3-6 weeks.

The upcoming release of Supabase Platform will use Postgres 17. The Postgres 17 bundle will no longer include the following Postgres extensions:

• timescaledb
• plv8
• plls
• plcoffee
• pgjwt

Existing projects will NOT be immediately impacted - the extensions will continue to be supported on Supabase Postgres 15, until the Supabase Platform “end of life” of Postgres 15 in approximately 1 year (May 2026). However, the extensions will not receive further updates and fixes. Existing projects will need to drop the extensions before they can upgrade to Postgres 17.

This decision to deprecate these extensions was not made lightly, however these extensions are more complex than “standard” Postgres extensions and require additional support/testing that did not match the usage we see on the platform.

To address the capability gaps left by deprecating plv8 and timescaledb, we plan to include the pg_partman extension in a future Postgres 17 release and will provide documentation to help migrate Timescale hypertables to native Postgres partitioning at that time. For plv8 we recommend porting the logic to Edge Functions, which offer greater scalability and flexibility. These changes are part of our ongoing efforts to streamline our platform, reduce operational complexity, and ensure long-term support for features that align closely with our user base.

If you have additional use-cases for these deprecated extensions, please reach out to us and our Success team will work with you to find a solution.

[!NOTE] This change has now been fully rolled out - thank you everyone for the feedback! 🙏

Tabs for Table and SQL Editor#

For those who've been with us since the very beginning, you might remember that we used to have tabs in the Table Editor which we eventually removed 😉 We're bringing this nifty UX back with a better UX too, and also introducing this into the SQL Editor as well! Conveniently go between tables across schemas, or flip between snippets without having to navigate through your list of queries (especially if you've got tons of them!)

These are currently behind their own feature previews at the moment, which you can access by clicking on your Profile picture in the top navigation bar, but we're going to be looking into an incremental rollout for everyone! Feel free to let us know what you think! 🙏

What we'd like to know from you#

• Any bugs or issues that you might have run into while using the new UI
• Any ideas or suggestions that you reckon will improve the DX based on how you use these 2 editors
• Feel free to leave any feedback in this thread too!

Rollout plan#

• Changes are behind a feature preview in the dashboard
• Starting from 12th May 2025, we will roll out to the hosted platform first as incremental % rollout where users will be opted into the feature preview by default
• If you might want opt out of the changes, you may disable the changes via the feature previews which you can access through the user dropdown in the header here:

Here’s everything that happened with Supabase in the last month:

Project scoped roles#

Project scoped roles are now available for all Supabase Team plans. Each member in the organization can be assigned a role scoped to the organization or to specific projects.

[GitHub]

MCP Server now works with VS Code#

Set up the Supabase MCP server to work with Visual Studio Code.

[Twitter]

MCP Server can now create and deploy Edge Functions#

Use the Supabase MCP server to build Edge Functions.

[Twitter]

Supabase UI Library now includes Infinite Query block#

React hook for infinite lists that fetches data from Supabase. Use it for infinite scroll.

[Link] [Twitter]

Supabase UI Library now includes Social Auth#

A block to quickly create authentication UI for all supported social logins.

[Link] [Twitter]

Quick Product Announcements#

• The new Supabase SOC 2 report is available. [Link]
• We published comprehensive documentation about our security processes and controls. [Docs]

Made with Supabase#

• Web application for creating and editing AI-generated avatars using OpenAI's DALL-E API. Built with React, TypeScript, and Supabase. [GitHub]
• Data transformation systems engineered for your needs [GitHub] [Website]
• Command line for finding lines that have specific keywords in Rust . [GitHub]

Community Highlights#

• Create a Reusable Team component for your application using Next.js, Supabase, and Shadcn [Article]
• Grocery Tracker App using Vue JS and Supabase [Article]
• Use Supabase MCP in VSCode and Cursor [Article]
• Supabase WordPress Integration - SupaWP Plugin [Article]
• Implementing multi-tenancy into a Supabase app with Clerk [Article]
• Build This Self-Expanding YouTube-Powered AI Agent Knowledge Base (n8n + Supabase) [YouTube]
• Custom SMTP for Supabase Email Authentication | Complete Setup + Testing [YouTube]
• AI Chatbot That Remembers You! (n8n + Supabase + WhatsApp) [YouTube]
• Building a MCP-Powered Task Manager Agent with Agno and Supabase: A Step-by-Step Guide [Article]
• How to Build an App From SCRATCH with Lovable + Supabase [YouTube]

Sort columns in the Table Editor through the column header#

We've integrated the sorting functionality into the column menu - and these will dynamically update based on the current sort state of the column!

PR: https://github.com/supabase/supabase/pull/35139

Link: https://supabase.com/dashboard/project/_/editor

Ability to add billing address when creating or upgrading an organization#

You can now set your billing address when creating or upgrading your organization, and also set a billing name that diverges from your organization name! In hopes of alleviating a common request where invoices needed to be amended as there wasn't a billing address set 🙂🙏

PR: https://github.com/supabase/supabase/pull/34922

Link: https://supabase.com/dashboard/new

Other bugs fixes and improvements#

General

• Add reset database password callout to Connect modal (PR)

Table Editor

• (Feature Preview) Fix searching in table editor unintentional clears all tabs (PR)
• (Feature Preview) Fix tabs order not persisting when a tab is closed (PR)
• (Feature Preview) Sync tab labels whenever reopening table editor (SQL Editor too) (PR)
• Fix table editor rendering multiple columns if the column has multiple identical constraints on it (PR)
• Fix inability to export data when all rows are selected (PR)

SQL Editor

• (Feature Preview) Fix snippets being renamed by AI not updating it's tab label (PR)

Storage Explorer

• Fix footer in list view unintentionally hiding last item (PR)

Edge Functions

• Fix logs refresh button not pulling latest data when "Last n" option is selected (PR)

Logs

• Fix datepicker overriding copy events (PR)

Integrations

• Add link to foreign table in table editor from wrappers (PR)

Custom Reports

• Fix missing labels on SQL blocks (PR)

Project scoped roles are now available for all Supabase Team plans.

With project scoped roles, you can:

• Restrict team member access to specific projects
• Set different permission levels for different projects
• Maintain better security boundaries within your organization
• Simplify compliance requirements, including HIPAA

Each member in the organization can be assigned a role scoped to the organization or to specific projects. If the member has a role at the organization level, they will have the equivalent permissions for that role across all current and future projects in the organization.

With project scoped permissions, you can assign members to roles scoped to specific projects within your organization.

To get started with project scoped roles visit your organization's team settings page to add users and manage their roles. If you're adding project scoped roles for a new user, you can only select one project when sending the invite. You can assign roles to multiple projects after the user accepts the invite.

(Upcoming) Dashboard layout update for organizations#

We've updated the layout of the dashboard in hopes to improve the UX for managing team members and billing for organizations, as well as to clearly show the relationship between organizations and their projects. The home page of the dashboard is now scoped to a selected organization instead of showing all projects across all organizations, and accessing organization settings are now in individual links in the side navigation bar.

This isn't publicly available just yet, but we're looking to incrementally roll this out to everyone in batches over the next few weeks, starting as a feature preview initially where you can opt in to experience the updated layout. We'd also love to hear any thoughts or feedback that you might have - do feel free to reach out to us! We're just a message away from the Feedback button at the top right corner of the dashboard 🙏🙂

PR: https://github.com/supabase/supabase/pull/33150

Link: https://supabase.com/dashboard

Revamped billing breakdown in organization settings#

As with our commitment to making billing as transparent as possible, we've made a number of improvements to the billing breakdown section under your organization settings, such as adding individual documentation links to each usage items charged, adding separate items for read replicas / branching, and more! Read more details about the changes if you might be interested in the attached PR below 🙂

PR: https://github.com/supabase/supabase/pull/34861

Link: https://supabase.com/dashboard/org/_/billing

Add Database upgrade logs#

We've added the ability to browse logs relating to database upgrade operations as a way to troubleshoot failed upgrades. Unsuccessful database upgrades are reflected with an alert on the project's home page which now also includes a link to the database upgrade logs along with the exact time interval when the upgrade took place. 🛠️ 🚧

PR: https://github.com/supabase/supabase/pull/27924

Link: https://supabase.com/dashboard/project/_/logs/pg-upgrade-logs

Feature previews are now available on local / self-hosted Studio#

Feature previews have always been available only for the hosted version of the dashboard, but we've decided to make it available for local / self-hosted version of the dashboard too!(Studio) Only feature previews that are relevant to the project will be present, so you'll be able to start using the Tabs interfaces for the Table Editor and SQL Editor soon once we've cut a new release 😉

PR: https://github.com/supabase/supabase/pull/35060

Other bug fixes and improvements#

Table Editor

• Clean up filters and sorts if applied on a column that has been deleted (PR)
• Optimize row retrieval with CTE to improve load times by almost 30x on larger tables (PR)

SQL Editor

• (Feature Preview) Persist scroll position when switching between snippet tabs (PR)
• Fix missing styles when multiple snippets are selected via shift click (PR)

Reports

• Support dragging a SQL chart from the Assistant into an empty custom report (PR)

Logs

• Consolidate date picker in logs to a single UI (PR)
• Add "Last 3 hours" option (PR)
• Add "Copy as JSON" button when view log details (PR)
• Add hint and query details to Postgres Logs (PR)
• Fix cmd+z undo behaviour in logs explorer (PR)

Integrations

• Add meters table for Stripe FDW (PR)
• Add Slack FDW (PR)
• Add Cloudflare D1 FDW (PR)
• Add Hubspot FDW (PR)
• Add Orb FDW (PR)

Here’s a recap of everything we announced during Launch Week and the month of March:

Supabase MCP Server#

We are launching an official Supabase MCP server. You can use this server to connect your favorite AI tools (such as Cursor or Claude) directly with Supabase.

[Link] [GitHub]

Supabase UI Library#

A set of convenient components built on shadcn that can be dropped into any Next.js, React Router, Tanstack Start, or vanilla React application. This initial release includes the following components:

• Password-based authentication
• File Upload Dropzone
• Realtime Cursor Sharing
• Current User Avatar
• Realtime Avatar Stack
• Realtime Chat

[Link]

Supabase Studio Improvements#

We shipped a number of Supabase Studio improvements and new features. Here’s a quick rundown of what’s new:

• Tabs!: The Table Editor and SQL Editor now have tabs!
• Customizable Reports: create reports to show data exactly how you want to see it
• SQL Blocks in Custom reports: use SQL Snippets in blocks inside your custom reports
• Inline SQL Editor: use a mini SQL Editor anywhere in the Dashboard
• Multiple AI Assistant chats: maintain history of your Assistant chats
• Logs improvements: more detailed inspect panel, and stacked charts

[Link] [GitHub]

Edge Functions Deploy from the Supabase Dashboard#

You can now create, test, edit, and deploy Supabase Edge Functions directly from the Supabase Dashboard.

[Link]

Realtime Broadcast from Database#

Send messages based on changes in the Database, directly from the Database itself. Scale to support sending Database change messages to tens of thousands of users.

[Link]

Declarative Schemas#

Use declarative schemas to define your database structure in a clear, centralized, and version-controlled manner.

[Link]

Postgres Language Server#

Postgres Language Server provides a collection of language tools and a Language Server Protocol (LSP) implementation for Postgres, focusing on developer experience and reliable SQL tooling. Today, we support autocompletion, syntax error highlighting, type-checking, and a linter.

[Link]

Quick Product Announcements#

• We expanded our official Third-party Auth integrations to include Clerk. We also made Third-party Auth cheaper so that it has pricing parity with Supabase Auth. [Link]
• We have added Deno 2.1 support for Supabase Edge Runtime. With Deno 2.1, you can use built-in tools to scaffold a new project, manage dependencies, run tests, and lints. [Link]
• You can now automate generation and updates of embeddings in your database. [Link] [Docs]
• Geo-aware routing for Supabase API Load Balancer optimizes requests performance for your globally distributed users. [Link]
• Dedicated Poolers are now available in Supabase for everyone on the Pro Plan and above. [Blog] [Link]
• The Supabase docs now support type hints. [Link]

Launch Week Hackathon Winners#

• AI RPG - An Interactive storytelling platform that enables players to create and play through AI-generated narrative adventures. [Tweet]
• AI Travel Concierge - An app that helps you travel by suggesting destinations and attractions and planning them. [Tweet]
• CiteAnalytics - A web analytics tool that tracks when LLM visits your website. [Tweet]
• play.theplaylist - Create YouTube playlists with an interactive UI and easily share it with friends. [Tweet]
• sendit - A social media content creation tool to refine posts using AI. [Tweet]
• StoryTime - Generate educational stories for kids using AI. [Tweet]
• Supabadge - Generate your own beautiful Supabase event badge! [Tweet]
• SupaQuery - Supabase SQL editor with Vim support. [Tweet]
• QuickAudit - An app that logs every DB change (INSERT/UPDATE/DELETE) for auditing. [Tweet]
• Today’s Diary - A diary app with a minimalistic UI that lets you exchange diary entries with another random user every day. [Tweet]

Made with Supabase#

• MagiCan - Finalist of our Lovable x Supabase hackathon. An infinite canvas platform that revolutionizes collaborative storytelling and project planning with advanced AI capabilities. [Website]
• Next.js + Stripe + Supabase A Production-Ready Template - Start building with authentication and payments in minutes. [GitHub] [Website]
• Hono Supabase Auth Example - This example shows how to use Supabase Auth both on the client and server side with Hono. [GitHub]
• Discover exactly when you can achieve financial independence with FireCalculator a precision calculator and visualization tools. [Website]

Community Highlights#

• Implementing multi-tenancy into a Supabase app with Clerk [Link]
• Supabase Just Dropped Their Own Fullstack UI Library! [YouTube]
• Generating and Storing Google Gemini Embeddings with Vercel AI SDK and Supabase [Link]
• Secure Your Next.js App: Email & Google Authentication with Supabase, PostgreSQL RLS, and Triggers [Link]
• Supabase just dropped an official MCP Server [YouTube]

What better way to wrap up Launch Week 14 than a summary of what was shipped to the dashboard (as well as several other goodies that we also shipped behind the scenes 😉)

Manage your Edge Functions directly from the dashboard#

You can now create and update your Edge Functions directly from the dashboard! We've introduced a new "Code" tab to the Edge Functions details page, which makes it possible to view and edit your Edge Function source code, then deploy the changes.

PRs:

• https://github.com/supabase/supabase/pull/33726
• https://github.com/supabase/supabase/pull/33727

Link: https://supabase.com/dashboard/project/_/functions

Test your Edge Functions from the dashboard too!#

To put the cherry on top, we've also introduced an Edge Function tester (which is basically a simplified version of Postman) that can be used to send requests to an Edge Function for testing. Access this UI by hitting the "Test" button while in an Edge Function 🙂

PR: https://github.com/supabase/supabase/pull/33728

Link: https://supabase.com/dashboard/project/_/functions

Tabs for the Table Editor and SQL Editor#

For those who've been with us since the very beginning, you might remember that we used to have tabs in the Table Editor which we eventually removed 😉 We're bringing this nifty UX back with a better UX too, and also introducing this into the SQL Editor as well! Conveniently go between tables across schemas, or flip between snippets without having to navigate through your list of queries (especially if you've got tons of them!)

These are currently behind their own feature previews at the moment, which you can access by clicking on your Profile picture in the top navigation bar. Feel free to let us know what you think!

PR: https://github.com/supabase/supabase/pull/31071

Link: https://supabase.com/dashboard/project/_/editor

Support for multiple Assistant chats#

We've added the ability to create and store multiple chats per project! Switch contexts without losing your conversation with the Assisant, and come back easily from where you left off thereafter too! Chats are also now scoped per project, so switching project also switches the chat.

PR: https://github.com/supabase/supabase/pull/34011

Link: https://supabase.com/dashboard/project/_

Support updating your account's email address and unlink identities#

Account Information has now been replaced with Account Identities and it'll display what identities are linked to your account (either Email and/or GitHub, or SSO). We've also added support for changing your account's email address if you've got an Email identity with us.

PR: https://github.com/supabase/supabase/pull/33966

Link: https://supabase.com/dashboard/account/me

Support saving preference for navigation side bar expand behaviour#

We've received multiple feedback from users regarding the expansion behaviour of the side navigation bar while in a project, and realised there was an almost even split between individual preferences on how the side bar should behave (keep expanded, keep closed, or expand on hover). As such, we've decided to make this behaviour controllable to your own preference, available now in the account preferences page 😄

PR: https://github.com/supabase/supabase/pull/33612

Link: https://supabase.com/dashboard/project/_

Other bug fixes and improvements#

Account

• Fix selection of single date for audit logs not returning any results (PR)

AI Assistant

• Cache results in browser for the queries that are generated and ran (PR)

Table Editor

• Fix exporting tables with large amount of rows (PR)
• Fix updating a foreign key type while trying to add a foreign key at the same time (PR)

Logs

• Update Field Reference for logs to show parameters for Shared and Dedicated Pooler (PR)

Reports

• Add Dedicated Pooler connections to Database report (PR)

Storage Explorer

• Fix switching buckets while uploading files to not upload to the bucket that was switched to (PR)

Database

• Use TimestampInfo to show relative date and times for database backups (PR)

Project Integrations

• Add Notion FDW (PR)
• Add Clerk FDW (PR)

We will be enforcing stricter limitations on the v0 and v1 GET Project Logs endpoint:

The restrictions are as so:

• If neither ?iso_timestamp_start= nor ?iso_timestamp_end= is provided, the queried timestamp range will be the last 1 minute.
• If either ?iso_timestamp_start= or ?iso_timestamp_end= is provided, the queried timestamp range will be a 1 minute window either before or after the provided query parameter.
• If both ?iso_timestamp_start= and ?iso_timestamp_end= are provided, the maximum allowed queried timestamp range is 24 hours. The size of the permitted window may be subject to change in the future.

This change will go into effect at 2 April 12pm SGT (4am UTC).

Starting on April 4th, 2025, we will be enhancing the routing behavior for experimental routing on eligible Data API requests. This change affects GET requests to Data APIs only; the routing behavior for all other requests remains unchanged:

Current behavior: Round-robin distribution among all databases (primary and all read replicas) in your project

New behavior: Geo-routing that directs requests to the closest available database

This enhancement delivers a better experience for your users by minimizing latency to your project. You can maximize these benefits by strategically placing Read Replicas close to your major customer locations.

For more information on geo-routing and experimental routing, please visit our documentation

Today we’re announcing the official release of Dedicated Pooler - a PgBouncer instance co-located with your Postgres database for lower latency, better performance, and higher reliability.

This is available today for paid plans on the Supabase platform while free and paid plans continue to benefit from our Shared Pooler via Supavisor.

Why Dedicated Poolers#

We created Dedicated Poolers to give you the ultimate flexibility in choosing the right connection type for your specific use case.

Now you have three options for connecting to your database and you can mix and match depending on your use case:

1. Direct connections (All Plans): Recommended for when you are connecting using servers.
2. Shared Pooler (All Plans): Recommended for when you are connecting using serverless functions (like Next.js or AWS Lambda) and/or IPv6-only networks.
3. Dedicated Pooler (Paid Plans): Recommended for when you are connecting using serverless functions and you start to scale up. Available on Pro Plan and above.

How It Works#

• Dedicated Pooler (IPv6 Only) - Only transaction mode is available. For IPv4-only networks, purchase the IPv4 add on or use the Shared Pooler.
• Shared Pooler (IPv4 + IPv6) - Both transaction and session modes are available. Use this Pooler only for networks that don't support IPv4 or if you need prepared statements.
• Dedicated Pooler Prepared Statement Support (Coming Soon) - We plan to support prepared statements in transaction mode by upgrading all PgBouncer instances to version 1.21+.

Get started by navigating to your project’s Connect settings or learn more about Dedicated Poolers by reading the announcement or going through the docs.

On April 21, we are restricting certain SQL actions you can perform in your database’s auth, storage, and realtime schemas.

Why are we making these restrictions?#

Supabase Auth, Storage, and Realtime services each rely on their respective schemas in order to function properly.

These restrictions prevent unintended side effects like third-party tooling and user defined changes altering schemas or their objects, such as migration tables and database functions, that could disrupt or break functionality.

What this means for your project#

On April 21, you will no longer be able to perform the following actions on the auth, storage, and realtime schemas:

• Create tables and database functions
• Drop existing tables or database functions
• Create indexes on existing tables
• Perform destructive actions (i.e. INSERT, UPDATE, DELETE, TRUNCATE) on the following migration tables:
  • auth.schema_migrations
  • storage.migrations
  • realtime.schema_migrations
• Revoking privileges on tables in these schemas from API roles (e.g. anon)

However, you will still have permissions to perform the following actions:

• Create foreign keys referencing tables in the auth, storage, and realtime schemas
• Create RLS policies and database triggers on the following tables:
  • auth.audit_log_entries
  • auth.identities
  • auth.refresh_tokens
  • auth.sessions
  • auth.users
  • storage.buckets
  • storage.migrations
  • storage.objects
  • storage.s3_multipart_uploads
  • storage.s3_multipart_uploads_parts
  • realtime.messages

How to determine if you’re affected?#

• Run the following query to check if you created any tables in the auth, storage, and realtime schemas:

• Run the following query to check if you created any database functions in the auth, storage, and realtime schemas:

What you need to do#

If any of the above queries return a result, you must move them to either the public schema or a schema that you’ve created. Otherwise, they will be deleted.

• Here’s how you can move a table to another schema:

• Here’s how you can move a database function to another schema:

Additionally, if you're using Migrations or Branching, you'll need to patch your migrations to move these objects to your own schemas. E.g. if you have a migration 20250101000000_add_custom_table.sql like so:

Then you need to edit it locally into:

Then you'll need to repair the migration history on the linked project:

Here’s everything that happened with Supabase in the last month:

Deploy Edge Functions from the Supabase dashboard#

Write your Edge Function in the dashboard using the AI Assistant and deploy it directly.

[Link]

Deploy Edge Functions from the CLI#

Write your Edge Function locally and deploy it using the CLI and without having to install Docker.

[Link] [GitHub]

Deploy Edge Functions using the API#

AI tools and other products that integrate with Supabase can now deploy Edge Functions using the Supabase API.

[Link] [GitHub]

Connect AI tools and LLMs to Supabase#

We’ve published documentation on how to use the Model Context Protocol (MCP) to connect external AI tools to Supabase. Use natural language commands to perform operations in Supabase.

[Link] [Docs]

Third-party Auth is now less expensive#

We’ve increased the MAU quota for using third-party authentication providers so it’s easier (and more cost-effective) to start using Supabase with an existing project that uses another auth provider.

[Link]

New billing documentation#

Better explanations for how bills are computed, upgrading/downgrading subscriptions, and concepts such as Credits or Spend Caps.

[Docs]

Using Postgres as a Graph Database#

pgRouting is a Postgres extension that can be used to add basic graph functionality to Postgres.

[Blog Post]

Quick Product Announcements#

• Invoke the SQL Editor from anywhere in the Supabase Dashboard [Link]
• Read HubSpot data from within Postgres using the new FDW [Link]
• Read Notion data from within Postgres using the new FDW [Link]

Made with Supabase#

• Stripe SaaS OSS with Supabase. Launch Full-Stack Apps 100x Easier.[GitHub] [YouTube]
• Atomic CRM. The Open-Source CRM Toolkit for Personalized Solutions [GitHub] [Website]
• GymBrah. Run your fitness business without chaos [GitHub][Website]
• SQL Noir. Learn SQL by solving crimes [GitHub] [Website]

Community Highlights#

• Global Community Meetups [Sign up here]
• The easiest way to get started selling SaaS with Polar [Repo]
• Supabase 2025 Full Free Course [YouTube]
• Build the Reddit Clone with Supabase [YouTube]
• How to Use Cursor Agent and Supabase to Maximize Productivity [YouTube]
• Multilingual transcription Telegram bot using Supabase and ElevenLabs Scribe API [Demo][YouTube]
• Using Remotion Lambda with Supabase [Docs]

You can now try Deno 2.1 locally with Supabase CLI. The goal of local preview is to identify any regressions or missing functionality before we upgrade hosted version to Deno 2.1.

The hosted version still uses Deno 1.4+, and if you deploy functions written with Deno 2.1, some of the features may not work.

How to try#

• Install Deno 2.1 or newer version on your machine (https://docs.deno.com/runtime/getting_started/installation/)

• Go to your Supabase project. cd my-supabase-project

• Open supabase/config.toml and set deno_version = 2

• All your existing functions should work as before.

*To scaffold a new function as a Deno 2 project:

• Open supabase/config.toml and add the following:

• Open supabase/functions/hello-world/main.ts and modify line 10 to:

• Use npx supabase@beta functions serve --no-verify-jwt to start the dev server.

• Visit http://localhost:54321/functions/v1/hello-world.

• To run built-in tests, cd supabase/functions/hello-world; deno test

Please give it a try and report any bugs and feedback.

We are happy to announce that we are simplifying our pricing further by greatly increasing our Third-Party Auth quotas and aligning them with our regular auth quotas.

With Third-Party Auth, Supabase allows you to use a different Auth provider alongside Supabase Auth and have an integrated experience, without being forced to adopt Supabase Auth straight away. This is especially useful if you'd like to start using Supabase with an existing project that uses a different auth provider.

This change is effective immediately.

Inline Editor (Feature Preview)#

We're introducing a new inline editor that you may toggle through Feature Previews! 🙂 The inline editor can be used to run SQL wherever you are in the dashboard without taking you away from what you're doing. As usual, we'd love to hear what you think about this so please do feel free to share with us the good and (perhaps more importantly) the bad about this functionality right here in our GitHub discussions! 🙏 More details and information about this is also available there 😄

PR: https://github.com/supabase/supabase/pull/33541

Link: https://supabase.com/dashboard/project/_

Other bug fixes and improvements#

General

• Fix Assistant's usability for local / self-host environment (PR)

Auth

• Add context menu support for users to copy email or delete user (PR)
• Add link to open user logs in the Auth logs (PR)

Billing

• Support adding additional billing email address (PR)
• Add Logdrain Egress to Total Egress per day usage chart (PR)

Edge Functions

• Redirect back to main page of edge functions if navigating to a slug that doesn't exist (PR)

Advisors

• Remove unnecessary 2dp precision for ms values in Query Performance (PR)
• Fix retrieving indexes in use for a selected SELECT query (PR)

Schema Visualizer

• Support downloading current view as PNG (PR)

Storage

• Fix List view footer showing up top instead of the bottom, covering the first item in the list (PR)

Logs

• Allow users to click on a property of a selected log and add it to search (PR)
• Remember last visited route in the Logs section (PR)

Reports

• Add Supavisor connections to database reports (PR)

We have introduced two new API endpoints that allow you to deploy and update Edge Functions programmatically. This will be handy if you're building a Supabase integration or want to create an internal workflow without relying on Supabase CLI.

These are the same endpoints we use internally for Deploying Edge Functions from CLI without needing Docker and writing Edge Functions using AI assistant.

Deploy an Edge Function#

This endpoint allows you to deploy a function by providing source files and metadata in a multipart/form-data body. You can also provide a function slug as the query parameter. If an existing function for the same slug exists, it will be updated; otherwise, a new function will be created.

You can pass the bundleOnly=1 query parameter to return the response metadata to the bundled function without persisting it. This is useful if you want to bulk update multiple functions atomically. Check the next section for the new bulk update endpoint.

API reference: https://supabase.com/docs/reference/api/v1-deploy-a-function

Example:

After the function is created, you can immediately invoke it:

Bulk update Edge Functions#

This endpoint allows you to update multiple Edge Functions atomically.

When deploying multiple edge functions, we recommend calling the deploy endpoint with the bundleOnly=1 query parameter, collecting the responses and then calling bulk update endpoint to update them atomically.

API reference: https://supabase.com/docs/reference/api/v1-bulk-update-functions

Write and run queries from anywhere in the dashboard#

https://github.com/user-attachments/assets/5951fbb2-3db7-48e5-b4fa-7c83fbad3d2d

Today we are introducing a feature preview that gives you access to a new "inline editor". This is a SQL editor that is accessible from wherever you are in the dashboard. You can write or generate queries, run queries, view results, and save them to snippets if needed. It sits alongside other pages in the dashboard which makes it easy to reference tables, policies, functions, triggers etc while writing your queries.

As part of this preview we are also changing how you create and edit policies, triggers and functions to make use of this new inline editor. We often receive feedback around the existing UI based approach to creating policies, and our hope is that with the continued advancement of LLM's we can augment a plain SQL Editor with AI assistance vs needing a UI. The inline editor has access to an inline Assistant (press cmd + k while in editor) which will help you generate and modify queries.

To enable the feature preview, click your profile avatar, click feature previews and enable inline editor

What we'd like to know from you#

• When you use the inline editor, please tell us what you used it for, how the experience was, and what could be improved
• For each use case, try the inline assistant (via cmd + k) and provide feedback on the results. We want to continue to iterate on our prompts so that accuracy is as good as it can be
• How comfortable are you using an open editor with templates and AI guidance vs the existing UI based approach for policies and functions?
• Any other ideas or suggestions

[!NOTE] This change has now been fully rolled out - thank you everyone for the feedback! 🙏

We've made a significant proposal to enhance the Supabase Dashboard UX, ensuring that Organizations serve as the central hub for managing billing and member access. This update introduces clearer navigation between Organizations and Projects, providing a more intuitive experience for all users.

We encourage everyone to share their feedback in this discussion while we actively refine these changes.

Quick video demo#

https://github.com/user-attachments/assets/1492484b-b3f7-44c5-817c-3188689ef528

What’s Changed?#

Organization#

• Navigation will focus on 1 Organization at a time.
• When you are viewing an organization only the Projects for that Navigation will be visible.
• You can switch Organization by clicking the Organization picker on the top header.

Sidebar Updates#

• Separate sidebars for Projects and Organizations.
• The User Account Dropdown will be moved to the top right, and be always visible.

Improved Routing & Auto-Redirects#

• You will be redirected back to your last active organization when opening the Dashboard.
• Users without an organization will always be prompted to create one upon signup.
• If no organization is available, you will be prompted to create an organization.

New /organizations Page#

• Lists all organizations owned by the user.
• We may also support a page which shows all projects for all of your organizations.

Account Settings#

• Account settings moved out of the organization context.

Usage Banners & In-App Notifications#

• Consolidated banners at the top of the dashboard.
• Clear notifications about unpaid invoices in other organizations.
• Notifications will be filtered per active organization.

Self-hosting / Local#

• No major changes for self-hosting or local

Rollout#

• Changes are behind a feature preview in the dashboard
• We will roll out to the hosted platform first as incremental % rollout where users will be opted into the feature preview by default
• If you might want opt out of the changes, you may disable the changes via the feature previews which you can access through the user dropdown in the header here:

Feedback#

Please feel free to leave feedback in this thread.

We've introduced an experimental flag to the Supabase CLI, which allows you to deploy Edge Functions without running Docker.

How to use#

This also simplifies importing files outside the supabase/ directory within Edge Functions. Useful for monorepo setups where you want to share code between your frontend and Edge Functions.

For example, Given the directory layout below, you can import my-lib from either index.ts or deno.json.

The new flag is available from the Supabase CLI beta releases 2.13.3. Please check CLI upgrade guide on how to use the beta releases on your machine.

CI#

We also recommend using the --use-api flag if you deploy Edge Functions via CI. This should speed up the deploys as it no longer requires Docker and also solves a race condition previously occurred when deploying multiple functions in parallel.

Here's an example GitHub Action config:

Note: If you run into any issues with the --use-api, you can drop the flag to use the default Docker-based deploy mechanism.

Note 2: To run/ test Edge Functions locally (supabase functions serve), you will still need Docker. This only modifies deploy behavior.

Deploy Edge Functions via the Assistant#

https://github.com/user-attachments/assets/c567ecc2-8eed-4589-b077-f578ceaeb562

You can now get help with writing edge functions using the Assistant, and also deploy the suggested edge functions right from the dashboard! This is just the first step towards providing a convenient way to manage your edge functions through the dashboard instead of using solely through the CLI, so watch this space! 👀 🙂

PR: https://github.com/supabase/supabase/pull/33293

Link: https://supabase.com/dashboard/project/_

Update to Authentication settings location in the dashboard#

All authentication settings are now consolidated into in one place, which is within the Auth section of the dashboard. They were previously split between project settings and the authentication product page which created confusion and potentially hid functionalities that a user might be looking for. We'll eventually also follow up with similar efforts for other product settings to improve the general information architecture of the dashboard, in hopes to help make finding your way around the dashboard better! 😄🙏

PR: https://github.com/supabase/supabase/pull/33335

Link: https://supabase.com/dashboard/project/_/auth/users

Table Editor peek referencing row from the table#

Clicking "View reference row" from the Table Editor now shows the row in a Popover rather than opening the referencing table with the relevant filters applied. This is in hopes to make the UX less intrusive and abrupt - and we'd love to hear what you think! Feel free to leave any feedback either through the dashboard or right here in the discussions 🙂

PR: https://github.com/supabase/supabase/pull/33141

Link: https://supabase.com/dashboard/project/_/editor

Easy way to Fix "Security Definer view" warnings#

Views that were created in the public schema without specifying security invoker will normally have a warning in the Table Editor regarding its accessibility via the project's API. Understandably, the solution to address this might not be intuitive, especially if you're not familiar with Postgres. As such, we've added a convenient action to automatically address this warning by applying the necessary fixes.

PR: https://github.com/supabase/supabase/pull/33363

Link: https://supabase.com/dashboard/project/_/editor

Other bug fixes and improvements#

Table Editor

• Changing schemas will render the table editor empty state instead of persisting the currently viewed table to prevent confusion (PR)
• Add support for bytea data type (PR)

SQL Editor

• Each section's (Shared, Favorites, Private) opened/closed state now persists from where you left off (PR)
• Support duplicating a query (PR)
• Fix inability to scroll results section when query returns an error with a long message (PR)
• Opt to not clear search results when clicking on a query while searching (PR)
• Fix moving query to new folder (PR)

Database

• Fix database tables not showing foreign key relations when opening Edit Table panel for the first time (PR)

Reports

• Add refresh button to Custom reports, API report, Storage report and Database report (PR)

Webhooks

• Fix issue with saving values with quotes in http parameters and headers (PR)

Cron

• Support single quotes in cron job names (PR)

Advisors

• Support resetting query performance report on read replicas (PR)

Logs & Analytics

• Support navigating logs in the table with arrow keys (PR)

Here’s everything that happened with Supabase in the last month:

Third-party Auth with Firebase is now GA#

Use Firebase Auth with your Supabase projects. [Docs]

Easier to see errors in log charts#

Log charts in Supabase are now stacked with successes and errors on top of each other, and colored by type. [Link] [GitHub]

Enhanced type inference for JSON fields#

Set up custom types with supabase-js for more concise and accurate types that reflect your data. [GitHub]

Type validation for query filter values#

The Supabase TypeScript SDK will correctly validate all query filter values in  eq,  neq, and  in  methods. [GitHub] [Docs]

AI Prompt for writing Edge Functions#

A prompt to help generate Supabase Edge Functions following best practices that you can supply to Cursor, Copilot, and other AI coding tools. [Docs]

Quick Product Announcements#

• Free plans are now limited to 0.5GB per project instead of 0.5GB per account. Keep building! [GitHub]
• Now you can top up your credit balance through your organization's billing settings. [GitHub]
• Added 3 configurable parameters to control disk autoscaling. [GitHub]
• Easier to find queries in the SQL Editor. [GitHub]

Supabase is deprecating Fly’s Postgres offering managed by Supabase on April 11, 2025.

Why are we deprecating this offering?#

This deprecation enables us to focus on a new architecture for scale-to-zero databases, zero-downtime upgrades (more on this later), and more. Afterward, we’ll re-evaluate multi-cloud deployments beyond AWS, our current cloud provider.

What’s the current status of Fly Postgres on Supabase?#

We have disabled Fly Postgres signups and existing Fly Postgres customers will no longer be able to spin up new projects on Supabase. However, you can still access any existing Fly Postgres database.

What is the deprecation timeline?#

Before April 11:

You will still be able to access your existing Fly Postgres projects. We strongly recommend that you transition to Supabase’s or Fly’s native Postgres offering as soon as possible.

On April 11:

Your Fly Postgres projects are removed from our platform.

Reach out to our support if you have any questions or concerns regarding this deprecation.

Log charts now show stacked charts with total warnings and errors#

With stacked charts, you should now be able to get a better, faster glance at your logs' status, and also identify potential issues with incoming requests easily!

Link: https://supabase.com/dashboard/project/_/logs/edge-logs

PR: https://github.com/supabase/supabase/pull/32742

Additional parameters added to Disk Settings#

3 new configurable parameters have been added that can control the autoscale behaviour of your disk, namely:

• Autoscale growth percent: Refers to the percentage of current disk size to grow by
• Minimum increment: Refers to the minimum value to grow the disk size by when autoscaling
• Maximum disk size: Refers to the maximum size that your disk can grow to

These parameters can be configured anytime with no cooldown, and can be accessed under "Advanced disk settings" in your project settings "Compute and Disk"

Link: https://supabase.com/dashboard/project/_/settings/compute-and-disk

PR: https://github.com/supabase/supabase/pull/32628

SQL Editor searching now renders a flat list#

https://github.com/user-attachments/assets/3cd07693-882d-486b-b848-842d67d0316a

This addresses a UX problem whereby searching for snippets do not immediately surface results that might be within folders - with rendering a flat list instead, this should enable users to find what they need faster. Results are also no longer separated into "Shared", "Favorites", or "Private to make scanning through results easier.

Link: https://supabase.com/dashboard/project/_/sql/new

PR: https://github.com/supabase/supabase/pull/33064

Bug fixes and other improvements#

General

• More mobile responsiveness improvements (PR)

Advisors

• Show timing in seconds instead of ms if > 1000 ms (PR)
• Allow exporting advisor results to CSV, or copy as JSON / Markdown

Cron

• Show all cron jobs even those with no names (PR)
• Any changes made using the UI will reflect in the SQL snippet textbox to support further customization (PR)

Table Editor

• Fix a bug with Set to NOW CTA that was specifically happening only in certain timezones (PR)

SQL Editor

• Fix X axis labels with charting in SQL Editor (PR)
• Fix client crash issue when using a non-numerical column as the Y axis (PR)
• Opened / closed state of each section is now persisted (PR)
• Support duplicating a query (PR)

[!NOTE]
This is only relevant for Free Plan customers.

We've relaxed the Database Size limit on the Free Plan to be 0.5 GB per active project, rather than 0.5 GB for your entire Free Plan organization (previously included paused/deleted projects within your billing cycle). This will be beneficial in a few cases:

• When pausing or deleting projects, they will no longer count towards the Free Plan limit.
• When launching more than one project on the Free Plan, each project is allowed 0.5 GB Database Size, rather than a total of 0.5 GB (i.e. two projects using 0.25 GB).

Before Every project that has been active at some point in your billing cycle counts towards the 0.5 GB Database Size limit. If you've deleted a project, the average Database Size will still count towards your limit. We sum up the average Database Size of all projects that are/have been active in the billing cycle. Two projects with 0.5 GB Database Size each equal a Database Size usage of 1 GB and therefore exceed the Free Plan quota.

After We only limit active projects to a Database Size of 0.5 GB per project. Deleted or paused projects, even within the billing cycle, do not count towards your Database Size limits. As long as none of your active projects exceeds 0.5 GB Database Size, you'll stay within the Free Plan limits. Two projects with 0.5 GB Database Size each would still be within the Free Plan quota, as no project is exceeding 0.5 GB.

Welcome to 2025. Here’s everything that happened with Supabase in the last month:

Supabase Integrations Page#

We added an Integrations Section to the Dashboard. Inside you’ll find useful features, like our new Postgres modules: Cron Jobs and Queues.

[Changelog]

Fix Security and Performance Issues with AI#

The AI Assistant has a new ability: it can help you understand and resolve Security and Performance issues. The issue context is passed to the assistant, which explains the issue and suggests fixes.

[Check out the Security Advisor]

SQL Editor Inline AI Assistance#

When using the SQL Editor, you can now hit CMD+K to open an inline AI assistant that will help you make changes to your query. It will only make changes to whatever you have selected, but also has the surrounding context and can access schema, policy, and function information, if needed.

[Check out the SQL Editor]

Supabase Branching Available in Vercel Integration#

Vercel Branching Integration now works with Vercel Marketplace managed projects. You can synchronize environment variables for newly created branches to your Vercel projects, no matter whether the project was created directly in Supabase or through a Vercel dashboard.

[Changelog]

Database Connection Settings Redesigned#

The “Connect” dialog has moved to the top of the Dashboard. You can access your database connection settings from anywhere. The “Connection String” tab includes guidance on when to connect via direct connection, transaction pooler, and session pooler.

[Dashboard]

Query Cloudflare D1 from Your Supabase Database#

Cloudflare D1 is a serverless SQLite service. You can now query it from your Supabase database using our Wrappers service, along with other services like BigQuery, ClickHouse, Firebase, and Snowflake.

[Docs]

Quick Product Announcements#

Dashboard

• The Supabase Dashboard is now responsive. This is just a first step towards a more complete mobile experience. [Link]
• Granular Disk Size usage break down by Database/WAL/System [Changelog]

Edge Functions

• Use a custom NPM registry for Edge Function dependencies [Changelog]

Logs

• Log Explorer UI Overhaul [Changelog]

Connection Pooler

• Supavisor Session Mode on port 6543 will be deprecated on February 28, 2025 [Changelog]

Auth

• Slack v1 OAuth has been deprecated in favor of Slack (OIDC) [Changelog]

TypeScript users, here's a cool new feature! Starting from v2.48.0, defining custom types for JSON fields in supabase-js and using them with the JSON selector is now easier, making your code more type-safe and intuitive.

Quick Example#

Define your custom JSON type:

What You Get#

Now, when you query your data:

Get Started#

Start using this feature with our guides:

• Generating Types
• Typescript Support
• Helper Types for Tables and Joins

Supabase CLI 2.7.0 adds support for bundling Edge Functions with static files.

You can access bundled files via Deno's file-system APIs. Here's an example function that serves a PDF file.

Use cases#

• Use custom Wasm modules in your Edge Functions (check this guide for more details on how to write & use wasm modules in Edge Functions)
• Create paywalls for serving digital content like ebooks
• HTML email templates for sending emails using Edge Functions

How to configure#

You will need to add static files to the function's directory to bundle them. Then, in the supabase/config.toml file for the project, add these lines:

You can specify an array of files or use a glob pattern (eg: "./functions/email-templates/*.html")

Check the CLI configuration reference for more details: https://supabase.com/docs/guides/local-development/cli/config#functions.function_name.static_files

Note: This feature is currently not available with branching and will be added with the next stable release of the CLI.

If you're only using Transaction Mode on Connection Pooler port 6543 or already using Session Mode on port 5432 then no action is required.

On February 28, 2025, Supavisor (Supabase's Connection Pooler) is deprecating Session Mode on port 6543. After this date, port 6543 will only support Transaction Mode while port 5432 continues to support Session Mode.

We’re making this change because Session Mode is already available on port 5432 and this streamlines our connection pooler’s ports and their respective modes.

Required steps:

1. Update your application/database clients to use port 5432 for Session Mode.
2. In your project’s Database Settings (”Connection pooling configuration”), set “Pool Mode” to “Transaction” and click “Save” (please keep in mind that this will restart all your connections connected to the Pooler).

Please reach out to our support if you have any questions or concerns regarding this change.

UI Overhaul for Log Explorer log details#

https://github.com/user-attachments/assets/1f752ebc-a814-4f1c-845f-4659a0dc87d3

The changes here addresses some UX friction whereby depending on the query, the detail panel of the log would be hard to read. We've hence updated the log detail drawing to add better spacing, the option to expand rows, and also use our TimestampInfo tooltip in the UI as well!

PR: https://github.com/supabase/supabase/pull/31684

Link: https://supabase.com/dashboard/project/_/logs/explorer

Toggle for enabling connection via S3 protocol in Storage#

PR: https://github.com/supabase/supabase/pull/31209

Link: https://supabase.com/dashboard/project/_/settings/storage

Credit Balance Top Up#

It is now possible to top up your credit balance through your organization's billing settings. Read more about this in our discussions page here

PR: https://github.com/supabase/supabase/pull/32680

Link: https://supabase.green/dashboard/org/_/billing

Other bug fixes and improvements#

Auth

• Fix impersonation and searching users with single quotes (PR)

Advisors

• Add "Ask Assistant" CTA to advisor issues (PR)

SQL Editor

• Persist last selected database (PR)

Logs Explorer

• Add copy as CSV + JSON options (PR)

Edge Functions

• A number of general improvements (more details in the PR) (PR)

Cron

• Add last and next run for cron jobs (PR)

It is now possible to top up your credit balance through your organization's billing settings. On successful payment, an invoice will be issued and you'll be granted credits. Credits will be applied to future invoices only and are not refundable. The topped up credits do not expire.

This can be useful in many scenarios:

• Issues with recurring payments (i.e. due to Indian banking regulations)
• More control about how often your credit card gets charged
• Easier for some accounting departments
• Yearly upfront payments

If you run out of credits while you are still on a paid plan, your credit card will be charged as usual.

If you are interested in larger (>$1,000) credit packages, please reach out.

If you are using our TypeScript SDK with automatically generated types, you are in for a treat. Starting version 2.47.12, our @supabase/supabase-js SDK will correctly validate all query filter values in eq, neq and in methods. Including not only primitives, but enums as well. In both tables, views, and arbitrarily-nested relations.

When using enums, LSP auto-completion also works out-of-the-box now.

Want to start using them? See our guides for how to get started: https://supabase.com/docs/guides/api/rest/generating-types https://supabase.com/docs/reference/javascript/typescript-support

Some organizations require using all modules from a private NPM registry for security and compliance reasons. Edge Functions now supports configuring a private registry to load all NPM modules using the NPM_CONFIG_REGISTRY environment variable.

You can define a private registry in the project's .env file or directly specify it when running the deploy command:

You will need Supabase CLI version 2.2.8 or higher to use this feature.

Note that Edge Functions also supports importing private NPM packages (which can be published on any registry).

Check the Managing dependencies guide to learn more about how to configure and use external dependencies in your Edge Functions.

Improved mobile navigation for the dashboard#

https://github.com/user-attachments/assets/a2e1c815-6d65-486f-ae77-1d5993377c40

We've heard many feedback around mobile support for the dashboard and we're taking the first step towards supporting that 📱🙂 While this PR doesn't completely optimize the mobile UX for the dashboard, navigating around the dashboard on mobile is now supported! We'll definitely be looking into optimizing other parts of the dashboard for mobile use so stay tuned! 😉

PR: https://github.com/supabase/supabase/pull/31080

Link: https://supabase.com/dashboard

Inline completions via Assistant in SQL Editor#

In hopes to make the Assistant's UX more seamless while in the SQL editor, we've added support for adjusting your SQL snippets inline while in the SQL editor without having to open the Assistant panel. Highlight the section that you'd like to edit, and hit CMD / CTRL + K to pop open the inline prompt 💬 Less clicking, more typing!

PR: https://github.com/supabase/supabase/pull/30706

Link: https://supabase.com/dashboard/project/_/sql/new

Improve date time editing in Table Editor Grid#

We've also seen a couple of feedback around supporting copying and pasting raw date time values from the Table Editor. We've previously been using the browser native date time input field which we've realised have been less than optimal for the following reasons:

• Adjusting the value typically takes several clicks which can feel frustrating
• The precision of time values in JS does not match the precision of time values in Postgres
• The UX varies a lot across browsers since each browser has their own implementation of the native date time input

As such we've decided to move towards supporting editing your raw values for date, timestamp, and timestamptz type fields, with a helper tooltip to show the time formatted in UTC and your relative timezone. This UX also allows us to support setting values to NULL which we struggled to do so gracefully with native browser date time inputs. Hope this helps make editing your data via the Table Editor easier 🙏🙂 More screenshots available in the attached PR below!

PR: https://github.com/supabase/supabase/pull/31121

Link: https://supabase.com/dashboard/project/_/editor

Support for bulk delete users#

Also another feature that we've heard many requests for - you can now delete your users in bulk! Select the users that you'd like via the checkboxes and a button will appear to allow you to delete them all. There is, however, a temporary limitation that you may only delete up to 20 users at once, but we'll be looking into lifting this limitation eventually 🙂

PR: https://github.com/supabase/supabase/pull/31271

Link: https://supabase.com/dashboard/project/_/auth/users

Other bug fixes and improvements#

General

• Add ability for Assistant to retrieve database functions within a schema (PR)
• Limit local storage memory to 20 chat messages for Assistant (PR)
• Support scrolling up in chat while a new response is being streamed (PR)
• Adjust warnings for destructive prompts via the Assistant (PR)
• Assistant to adhere to Supabase Linter rules when generating responses (PR)

Table Editor

• Add dropdown menu item to copy table name (PR)

Launch Week 13 has wrapped up and it's now the holiday season! 🎄🎁 If you might have missed our launches last week - fret not! We've got you covered with a brief summary of the changes that landed in the dashboard right here 🙂

Dashboard Integrations#

You should have noticed by now, but we've added a new Integrations page where you can easily manage all things related to your database that may not necessarily be directly about your database. This allows us to consolidate some features that were in slightly odd places such as the GraphiQL IDE or Database Webhooks, and also provide UIs that are specific to certain database extension(s) such as Vault, or the newly added Queues and Crons (more on that below!). Database Wrappers have also been shifted here as well, and we hope that this shift will help make finding things around the dashboard easier for everyone 🙂🙏

Link: https://supabase.com/dashboard/project/_/integrations

PR: https://github.com/supabase/supabase/pull/30476

AI Assistant V2#

We've always had the AI assistant sprinkled around the dashboard in the SQL Editor, and RLS Editor. Today we're making it accessible from anywhere in the dashboard, spiced with several new abilities to go along with 🎁 Read more about this in our blog post and learn how you can leverage the assistant to get more done, and quicker! 😄

Blog Post: https://supabase.com/blog/supabase-ai-assistant-v2

Link: https://supabase.com/project/_

PR: https://github.com/supabase/supabase/pull/30523

Cron#

Create recurring jobs to run SQL snippets, or call database functions, Supabase Edge Functions, and even remote webhooks with our new Postgres Module, Cron! Supabase Cron is built on the powerful pg_cron extension by the team at Citus Data, and we appreciate the Citus Data for generously licensing their extension with the OSI-compatible PostgreSQL license, allowing us to support existing tools wherever possible. 💪🏻

Blog Post: https://supabase.com/blog/supabase-cron

Link: https://supabase.com/dashboard/project/_/integrations

PR: https://github.com/supabase/supabase/pull/29291

Queues#

Process and manage asynchronous tasks with Supabase Queues! This is a Postgres-native, durable Message Queue with guaranteed delivery, improving the scalability and resiliency of your applications, and it's designed to work seamlessly with the entire Supabase platform. Similarly to Cron, Supabase Queues is built on the pgmq extension by the team at Tembo, and we appreciate the Tembo team for licensing their extension with OSI-compatible PostgreSQL license as well! 🙏

Blog Post: https://supabase.com/blog/supabase-queues

Link: https://supabase.com/dashboard/project/_/integrations

PR: https://github.com/supabase/supabase/pull/30300

Restore to a new project#

You can now copy data easily from an existing Supabase project to an entirely new and independent one! This has been a well requested functionality and we're happy to share that it's finally possible to do so via the dashboard 🙂 Read more about this in our blog post, or in our documentation 🙏

Blog Post: https://supabase.com/blog/restore-to-a-new-project

Docs: https://supabase.com/docs/guides/platform/backups#restore-to-a-new-project

Link: https://supabase.com/dashboard/project/_/database/backups/restore-to-new-project

PR: https://github.com/supabase/supabase/pull/30325

Other bug fixes and improvements#

Table Editor

• Fix rendering of OID cell types causing a client crash (PR)

Dear Users,

Slack has deprecated their existing v1 API and will fully sunset the API over the next two years. This means that Slack Applications using the v1 Slack (Deprecated) provider will stop functioning if no action is taken. In turn, Supabase Auth users using the Slack (Deprecated) provider will also not be able to sign in via the Slack OAuth provider if no action is taken.

We’ve introduced a new replacement OAuth provider named “Slack (OIDC)” which supports the latest Slack API and will send out an email to affected users next week with instructions on how to migrate.

To migrate your authentication system, you'll need to:

1. Create a new Slack Application in your Slack dashboard
2. Update your credentials in the Supabase Dashboard by switching from the deprecated Slack (Deprecated) provider to the new Slack (OIDC) provider. You can find the provider in your project under Authentication > Providers > Slack (Deprecated)
3. Update your code to use the new provider in all OAuth calls, like this:

4. If you are using the Supabase CLI , you will also need to update your config.toml to use [auth.external.slack_oidc] in place of [auth.external.slack_oidc]. See the local development docs for a detailed example.

Refer to our documentation for further details

Further configuration of the deprecated Slack provider will not be possible past 15th Jan 2025 as we will remove Slack provider from the dashboard then. If you need more time to access the configuration page , reach out to us via a support ticket.

Slack will terminate support for Legacy bots and Classic Apps on March 31, 2025 and March 31, 2026 respectively.

Please reach out via support or on the thread if there are any questions or concerns.

Introduction#

We are removing app.settings.jwt_secret from the postgres database on 2024/11/22.

This setting has previously been available through our PostgREST integration, and could be accessed using current_setting('app.settings.jwt_secret') in SQL.

Why are we doing this?#

The jwt_secret can be used to mint new, custom JWTs and is security sensitive. Supabase limits access to the jwt_secret , through both the dashboard and API, to specific roles (owner, admin and developer). Allowing access to this setting directly in the database can allow bypassing of these restrictions.

What do you need to do?#

If you need the jwt_secret, it can be retrieved through the Supabase dashboard.

If you are using the app.settings.jwt_secret in SQL, you will need to update your function to retrieve this value from Vault.

Also, please consult the changelog entry for Asymmetric Keys to understand the coming changes to jwt_secret and how keys at Supabase are changing.

Table Editor Performance Improvements#

We've set aside some time to look into improving the performance of the Table Editor over the past few weeks, in particular shortening both perceived and actual loading times as you navigate around the Table Editor. This all comes together in several PRs as we explored from 2 angles:

• Optimizing the queries that are firing behind the scenes by removing redundant sections + minimise waterfall requests
• Introducing prefetching behaviours as your mouse cursor goes through the list of tables to have the tables' contents ready by the time you open it in the UI

Performance improvements have always been a consistent topic with the team, and we don't intend to stop here! Hopefully these changes will make it smoother and faster for you to build your project with the dashboard and as always let us know any feedback! 🙂🙏 Just a button away in the top right corner of the dashboard to get your thoughts heard 😄

PRs:

• Query optimizations Part 1: https://github.com/supabase/supabase/pull/30184
• Query optimizations Part 2: https://github.com/supabase/supabase/pull/30295
• Prefetching on the table editor: https://github.com/supabase/supabase/pull/29987
• Prefetching on the home page: https://github.com/supabase/supabase/pull/30317

Link: https://supabase.com/dashboard/project/_/editor

Other bug fixes and improvements#

Table Editor

• Simplified header when rows are selected (PR)
• Allow exporting of data on tables that are protected (PR)

Authentication

• Fixed provider "Enabled" state when viewing user details if user's provider is LinkedIn (PR)
• Sorting users on a column will shift users with NULL values on that column to the bottom (PR)
• Fix "Last signed in at" column showing up as "Waiting for verification" on subsequent pages as page is scrolled down (PR)

Storage

• Add ability to toggle image transformations from settings (PR)