Another brief summary of changes that went into the dashboard over the past 2 weeks, but before that...

Supabase Select just wrapped up over the weekend!#

If you might have missed it or want to get involved - Livestreams are available on the Supabase Youtube channel, or on our site here! A huge thank you to everyone in the community for joining us on this journey thus far - and as always let us know any feedback / ideas / thoughts, anything! We promise we look at every message that comes in 🙂🙏

Assistant Improvements#

We've been shipping some incremental improvements to the Assistant which involves both better response speeds, better quality outputs, and better UX with a more action-oriented approach (along with some style refinements to messages and tools)! 🤖🙂

These are all in hopes to support you while building out with Supabase and we're still looking into how we can make the experience even better for you! Feel free to leave any feedback or ideas in this thread on how we can further improve the Assistant 😄🙏

PR:

• https://github.com/supabase/supabase/pull/38806
• https://github.com/supabase/supabase/pull/38805
• https://github.com/supabase/supabase/pull/39031
• https://github.com/supabase/supabase/pull/39072

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

Contextual error handling in Table Editor#

Enabling users to self-debug when running into issues have been at the forefront of our priority recently - this is just a small addition to that topic in which we're opting to provide contextual errors in the table editor, specifically when applying filters 🙂🔍

Hopefully these will provide better clues while working with the Table Editor instead of just merely showing "Failed to retrieve rows" - and we're hoping to expand this further too to cover more cases! 🙏

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

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

Other bug fixes and improvements#

General

• Improve clarity of errors for organization member invite flow (PR)
• Fix deleting project not refreshing list of projects on home page (PR)

Table Editor

• Fix "New table" button not working if on an unknown table (PR)
• Improve stability of tab state syncing between URL params and local storage (PR)
• Use session storage as default cache for tab state (PR)
• Ensure CSV chunk uploads handle rate limits properly (PR)
• Refrain from applying a default sort on JSON columns (PR)
• Flatten copy cell and row actions in context menu (PR)

Storage Explorer

• Fix long bucket names blocking bucket actions (PR)

Integrations

• Fix webhooks HTTP headers for edge functions not loading Auth headers on first open (PR)

Advisors

• Query performance improve layout of metadata in query details panel (PR)
• Query performance consolidate time consumed and total time columns (PR)
• Query performance make query pattern expandable (PR)
• Query performance improve time consumed text to be more human readable (PR)

Reports

• Improve tooltip UX (PR)
• Make chart highlight actions configurable per chart (PR)
• Use is instead of matches in API filters (PR)
• Fix max pooler connections tooltip (PR)
• Always show tooltip values (PR)

What Changed#

We've consolidated all Supabase JS client libraries into a unified monorepo at supabase/supabase-js.

For Package Users 👥#

Nothing changed for you! Continue installing packages as usual:

For Contributors 🛠️#

All development now happens in the monorepo:

Old repositories (will be archived soon):

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

New location: All libraries are now under packages/core/ in supabase/supabase-js

Benefits#

• Fixed versioning - all packages share the same version for compatibility
• Atomic changes - fix bugs across libraries in single PRs
• Better testing - immediate integration testing without manual releases
• Unified tooling - consistent build, test, and release processes

Getting Started#

1. Fork and clone: github.com/supabase/supabase-js
2. Read the guides: Complete documentation in the new repository
3. Use Nx commands: npx nx test auth-js, npx nx build storage-js, etc.

Documentation#

All documentation is now in the monorepo:

• Contributing Guide - Development workflow and PR process
• Migration Guide - Detailed transition information
• Testing Guide - Package-specific testing requirements

Questions?#

• Issues: supabase-js Issues
• Migration help: Open a new issue. Add [migration] in the title of your issue.

Another brief summary of changes that went into the dashboard over the past 2 weeks! 🙂

Couple of improvements to the Query Performance Advisor#

We've been shipping incremental improvements to the Query Performance Advisor in hopes to simplify the usability of the report despite all the information present on the page 🙏🙂 There's quite a few tidbits there so check out the advisor and let us know what you think! Huge shoutout to @kemaldotearth for this one! 😄

PRs:

• https://github.com/supabase/supabase/pull/38470
• https://github.com/supabase/supabase/pull/38523
• https://github.com/supabase/supabase/pull/38606
• https://github.com/supabase/supabase/pull/38657
• https://github.com/supabase/supabase/pull/38634
• https://github.com/supabase/supabase/pull/38744
• https://github.com/supabase/supabase/pull/38778
• https://github.com/supabase/supabase/pull/38783
• https://github.com/supabase/supabase/pull/38819
• https://github.com/supabase/supabase/pull/38825
• https://github.com/supabase/supabase/pull/38815
• https://github.com/supabase/supabase/pull/38867
• https://github.com/supabase/supabase/pull/38920

URL: https://supabase.com/dashboard/project/_/advisors/query-performance

Configure to save Auth Audit Logs in project's database#

We've added a new page under the Auth section "Audit Logs" which will allow you to toggle disabling writing Auth audit logs to your project's database. The Auth audit logs will still be available in the auth logs but doing so will then prevent the audit logs from taking up your project's database space, which subsequently reduces your database storage costs. Read more about this in our docs here!

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

URL: https://supabase.com/dashboard/project/_/auth/audit-logs

Other bug fixes and improvements#

Table Editor

• Shift refresh button to top nav for better visibility (PR)
• CSV imports will show row number with the error to give a more actionable message (PR)
• Fix default value placeholder for fields with foreign keys (PR)
• Add support for expanding rows into a side panel for foreign tables (FDW) (PR)
• Add contextual errors for foreign tables if failed to fetch rows (FDW) (PR)

Integrations

• Fix webhooks HTTP headers for edge functions not loading auth headers on first open (PR)

Reports

• Chart highlight actions can be configured per chart (PR)

On July 24, 2025 Supabase deployed an updated version of our Data API (Postgrest) v13 that came with a more strict approach to JWT validation.

Some customers experienced issues when using custom JWT.

Recently, we published updates to our documentation at https://supabase.com/docs/guides/auth/jwts#verifying-with-the-legacy-jwt-secret-or-a-shared-secret-signing-key and https://supabase.com/docs/guides/auth/signing-keys#getting-started that give instructions on how to re-import the custom signing key, which will resolve this issue going forward.

Here's a brief summary of the changes that went into the Supabase dashboard over the past two weeks between the 18th of August to 1st September 2025! 🙏 As always - we promise that we read through every feedback that comes to us so don't hesitate to share any ideas or thoughts! 😄

Set expiration dates for Personal Access Tokens#

https://github.com/user-attachments/assets/7ba131ff-3fd6-4454-9d6f-85cd1049773a

You can now set an expiration date when creating Personal Access Tokens! Expiration can be configured using preset durations, a custom date (up to 1 year), or set to never expire. Feel free to leave any thoughts or feedback in our discussion here!

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

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

Sync tooltips in Reports across all charts#

You can now sync either chart headers and/or tooltips in your project's built-in reports to better visualize your data across different metrics at a specific point in time! This can be toggled with the settings button in the built-in reports pages (although the tooltip value break downs are available from the Team plan and above 🙂)

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

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

UI update to Auth RLS policies page#

As part of an ongoing effort to improve consistency of the dashboard layouts across all pages, the UI of the Auth Policies page has been updated, and the changes further emphasizes tables with RLS disabled with an amber accent. Let us know what you think! 🙂🙏

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

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

UI update to Integrations page#

Similar to the above, the project Integrations page has also gotten an update to bring the UX and layout closer to other parts of the dashboard. Cron and Queue integrations have also been updated to use the Data Grid for listing cron jobs and queues 😄

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

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

Assistant UI Refinements to improve transparency of tool calls#

We've made some adjustments to the UI of the Assistant as well as the prompt rendering to improve readability, but importantly also looked into enhancing the transparency of tools calls by the Assistant which aims to reveal the thought process of the Assistant.

We're constantly trying to improve the Assistant's response quality and are currently still in the process of tweaking things in hopes to support you working with Supabase and Postgres better! 💪🏻 If you might have any ideas or feedback from using the Assistant, don't hesitate to leave them in this thread! 😄

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

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

Other bug fixes and improvements#

Account Preferences

• Updated layout of account preferences pages to improve consistency of IA (PR)
• Support for updating profile's username and primary email (PR)

AI Assistant Shoutout to @taishikato for the contributions here - we really appreciate it! 🙂🙏

• Added support for editing messages to the Assistant (PR)
• Added support for deleting messages to the Assistant (PR)
• Added support to stop Assistant responses mid stream (PR)

Table Editor

• Fix CSV import for Postgres array types (PR)
• Fix copy action copies whole cell value even if only a subset of the value is highlighted while editing cell (PR)

SQL Editor

• Search list items now have context menu support (PR)
• Fix searching doesn't show snippets that are within folders (PR)

Storage Explorer

• Prevent creating folders of the same name but different casing (PR)
• Fix editing a bucket not selecting the right unit if a bucket had a file size limit greater than 1KB (PR)

Reports

• Updated chart colors to improve contrast (PR)

General Shoutout to @saeris for multiple contributions towards cleaning up our code base with replacing deprecated components and improving our UI consistency across the dashboard! Thank you so much! 😄🙏

• General cleaning up of deprecated components + improving UI consistency (Changes)
• Added table view for organizations project's page (PR)
• QOL UX improvement to tables by adding shadows on inner scroll if there's more contents available (PR)

You can now set an expiration date when creating Personal Access Tokens. Expiration can be configured using preset durations, a custom date (up to 1 year), or set to never expire.

Additionally, token usage is now tracked (with updates up to every 15 minutes), making it easier to identify unused tokens and safely remove them.

https://github.com/user-attachments/assets/7ba131ff-3fd6-4454-9d6f-85cd1049773a

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.

📢 UPDATE [November 26, 2025]: Public beta is live now!

• See the latest comment below for full details

---

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: Public Beta

Target Date:

• Generally available: Q4 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.

After 10 hectic months of building, Supabase is now in Beta.

This is also available as a blog post and a video demo.

Supabase is now in Beta#

We spent months working on Performance, Security, and Reliability. Read more on our Beta Page.

Improve your docs inline#

Add comments and descriptions to your Tables directly from our auto-generated docs.

Table View now has realtime changes#

Any updates that happen to your database are reflected in the Table View immediately.

Table Pagination#

Our table view now has pagination - better for working with large data sets.

Supabase raised a Seed Round#

We raised $6M from Y Combinator, Mozilla, and Coatue. You can read more on TechCrunch.

Kaizen#

• Supabase is now 26% faster in regions which support Graviton (1460 reqs/s up from 1167 reqs/s)
• We launched a new region in Sao Paulo.
• Postgres Array Support. You can now edit Native Postgres array items in the grid editor or the side panel.
• We added better support for your custom Database Types.
• Fixed some buggy keyboard commands. We're continuously improving key commands in the Table editor.

We've been building for 9 months now, are we're getting even closer to Beta.

This is also available as a blog post and a video demo.

Add users#

You can now add users manually from your dashboard.

User admin#

You can also perform admin functions on existing users - send password reset emails, magic links, and delete users.

Even more powerful SQL Editor#

Last month we announced an improved SQL Editor, and this month we've taken it even further. The SQL Editor is now a full Monaco editor, like you'd find in VS Code. Build your database directly from the browser.

Status page#

We added a Status Page which tracks the uptime and latency of the Supabase platform.

Kaizen#

• We completed a security audit by DigitalXRAID.
• Email confirmations now enabled by default for signups.
• Updated Benchmarking Suite to include more realistic workloads, on various different servers (results published soon).
• You can now set/edit/remove Foreign Keys via the table editor.

We're now 8 months into building Supabase. We're focused on performance, stability, and reliability but that hasn't prevented us from shipping some great features.

This is also available as a blog post and a video demo.

Supabase.js 1.0#

In the lead-up to our Beta launch, we've released supabase-js version 1.0 and it comes with some major Developer Experience improvements. We received a lot of feedback from the community and we've incorporated it into our client libraries for our 1.0 release.

Check out the blog post to learn more.

More powerful SQL Editor#

Although it was only intended to be a temporary feature, the SQL Editor has become one of the most useful features of Supabase. This month we decided to make give it some attention, adding Tabs and making it full-screen. This is the first of many updates, we've got some exciting things planned for the SQL Editor.

Keyboard shortcuts for Power Users#

For the heavy table editor users, we've gone ahead and added a bunch of key commands and keyboard shortcuts so you can zip around and manipulate your tables faster than ever.

Magic Links#

One of the most requested Auth features was the ability to send magic links that your users can use to log in. You can use this with new or existing users, and alongside passwords or stand alone.

Kaizen#

• We have new and improved docs.
• We converted realtime-js to TypeScript.
• Dashboard Performance: we heavily optimised our dashboard routes.
• With the help of the community, we closed a lot of issues during Hacktoberfest.
• We have started benchmarking all the open source tools we use. We'll publish the results this month.

This is also available as a blog post.

Third-party logins#

We've released OAuth logins! You can now enable third-party logins on your app for Bitbucket, GitHub, GitLab, or Google.

Clone tables#

You can duplicate your tables, just like you would inside a spreadsheet.

Enable and disable extensions#

Extensions are easier to use. You can enable Postgres extensions with the click of a button.

Save your favorite queries#

The SQL editor now stores your query history in your browser. You can also save your favorite queries to run later!

GitHub Discussions#

Supabase was given access to GitHub Discussions! This is the place for you to ask questions or show off what you've built with Supabase.

Kaizen#

• Our dashboard now uses Next.js automatic static optimization - so it should be noticeably more responsive.
• We created an Isomorphic gotrue-js TypeScript library for interacting with Netlify's GoTrue server. This will soon be bundled into supabase-js
• We migrated our postgrest-js library to TypeScript, and it will soon be bundled into supabase-js

This is also available as a blog post.

We're 6 months into building our hosted database platform and we've made some major improvements to our auth system and table view.

Easily create tables#

Set up tables and columns directly from the table view.

Invite your team#

You can now invite team members to your organisation.

Auth: Email Confirmations#

You can now enable Email Confirmations for new users. This can be toggled on or off and the template for this email can be edited via the dashboard.

Typescript support#

The biggest communty contribution to date, @thorwebdev added Typescript support to Supabase. He even live streamed the process.

Kaizen#

We have a number of small improvements:

• supabase-js now has UMD support
• We significantly improved our docs. Try out the new search!
• All of our awesome sponsors are now listed on our OSS page.

Supabase July Alpha Updates#

This is also available as a full blog post with videos.

After 5 months of building, we're releasing one of our most anticipated features: Supabase Auth.

Auth#

This month, we're ecstatic to announce a feature we think you'll love: Supabase Auth. It's too big to fit into a monthly update so look out for a full update in the next few days.

We want to make it easy to get started adding Auth to your app, so we've released a simple example and a video tutorial which shows you how to implement a basic auth system using PostgreSQL's Row Level Security.

Table Editor#

We've made some massive improvements to our Table Editor that we're excited to share.

Relationship drill down#

Last month we made it easy to drill into your table relationships. This month, we make it possible to drill multiple levels deep.

Add, delete, and download rows#

We're making it easier to manipulate your data. Next month, you'll be able to add and remove columns directly from the Table view.

New Postgres Extensions#

If you launch a new Supabase project, you'll have access to several new Postgres extensions:

• pgsql-http: HTTP client for PostgreSQL, retrieve a web page from inside the database.
• pgjwt: PostgreSQL implementation of JSON Web Tokens
• plpgsql_check: a linter tool for language PL/pgSQL
• pljava: write Java in your stored procedures, triggers, and functions

Kaizen#

We have a number of small improvements:

• Added Auth documentation to the auto-generated docs in each project
• Added a new or filter to the client library
• Table View now remembers which tabs you had open.
• We have released a lot of new functionality to pg-api, a server for for managing Postgres internals via a REST interface.
• Performance: the "flash of black" which was appearing on page transition is now gone

Supabase June Alpha Updates#

This is also available as a full blog post with videos.

We're now 4 months into building Supabase, which means another major update. Here's a few things we think you'll love in this release.

View relational data#

We're sometimes asked how we will make Postgres as simple as Firebase, since Postgres is a relational database. This month we're making our first steps to prove that relational databases can be even easier to use than document stores. We're releasing an excel-like editing interface which can drill down into your relational data.

Manage JSON data#

Postgres is an amazing database, giving the flexibility of a document store with the power of a RDBMS. If you use JSON data in Postgres, then we want to make that easy too. Supabase detects when your column is JSON or JSONB, and provides an easy way to edit and view your data. More improvements coming soon for this feature!

Choose your region#

If you noticed a bit of latency on Supabase, it's because your projects were previously set up in Singapore. It was always our intention that you'd be able to choose your database region, and this month we've delivered it. In the next releases we'll even allow you to go multi-region, instantly replicating your database close to your customers.

Backups#

A guiding principle at Supabase is zero lock-in. So this month we are exposing your daily database backups on the dashboard, giving you a simple way to migrate off Supabase. We have a lot more to build in this space (WAL-G!), so watch this space.