Changelog

The Supabase Management API logs.all endpoint is removed on 2026-09-23. Scripts calling it must migrate to the new ClickHouse-backed logs endpoint, which accepts ClickHouse SQL only.

Self-hosted Supabase makes Envoy the default API gateway, replacing Kong, the week of 2026-08-09. Opt back into Kong if you rely on its HTTPS listener, a custom kong.yml, or the kong service name.

Postgres log_connections defaults to off for new projects and existing Free and Pro projects from 2026-07-09, cutting log noise. Re-enable it via the dashboard or Management API.

From 2026-06-03, new Free plan projects using Supabase's default SMTP cannot customize auth email templates. Existing projects keep theirs. Configure a custom SMTP provider to customize.

Supabase Auth now supports passkeys (Beta): passwordless, phishing-resistant sign-in built on WebAuthn using biometrics, a device PIN, or a hardware security key. No action required.

Supabase support for Postgres 14 ends on 2026-07-01. Projects still on Postgres 14 will be upgraded automatically; projects using removed extensions (timescaledb, plv8, pgjwt) will be paused.

Supabase's OAuth token endpoint /v1/oauth/token returns HTTP 200 instead of 201 starting 1 June 2026. Check for any 2XX status (response.ok), not a hardcoded 201.

Supabase will add applicable taxes (VAT, GST, sales tax) to invoices based on each organization's billing address, rolling out from 1 May to 30 June 2026. Review your billing address and Tax ID.

pg_graphql will be disabled by default on new Supabase projects, and on existing projects older than 30 days with zero GraphQL traffic. Re-enable it via Database Extensions if needed.

Developer Update for December 2025: Supabase ETL, Analytics and Vector Buckets, iceberg-js, Supabase Platform, OAuth 2.1 provider, Kiro integration, and AWS Marketplace listing.

Supabase Storage splits egress into cached and origin tiers with separate quotas. Cached egress is now $0.03 per GB, three times cheaper than origin egress, on Free and paid plans.

The upcoming Supabase Postgres 17 bundle drops timescaledb, plv8, plls, plcoffee, and pgjwt. Postgres 15 keeps the extensions until end of life around May 2026; drop them before upgrading.

On 2025-04-02 the Supabase Management API GET /projects/{ref}/analytics/endpoints/logs.all defaults to a one-minute window and caps explicit ranges at 24 hours. Update clients querying wider ranges.

On 2025-04-04 the Supabase Data API switches experimental routing for GET requests from round-robin across all replicas to geo-routing that targets the nearest available database, lowering latency.

Supabase Dedicated Pooler is now generally available on Pro and above: a co-located PgBouncer instance with lower latency than the Shared Pooler for serverless workloads. Transaction mode, IPv6 only.

Supabase developer update for February 2025: deploy Edge Functions from the dashboard, CLI, or Management API; new Model Context Protocol docs; and cheaper third-party Auth quotas.

Supabase third-party Auth quotas now match standard Auth: 50,000 MAU on the Free Plan and 100,000 MAU on Pro and Team. Overage stays at $0.00325 per MAU. Effective immediately, no action required.

Supabase is deprecating Fly.io Postgres managed by Supabase on 2025-04-11. Signups are disabled; existing projects are removed on that date. Migrate to Supabase Postgres or Fly native Postgres.

The Supabase Free Plan 0.5 GB database size limit now applies per active project rather than per organization. Paused and deleted projects no longer count toward the cap. Effective immediately.

Supabase organizations can now top up their credit balance from billing settings. Topped-up credits never expire, apply to future invoices only, and are not refundable. Available on all paid plans.

Supavisor deprecates Session Mode on port 6543 on 2025-02-28; after that date port 6543 only supports Transaction Mode. Move Session Mode clients to port 5432. Transaction-only users need no action.

Supabase docs now split into Build and Manage top-level menus, with a new Deployment section and a Monitoring and troubleshooting section to make features and guides easier to find.

The Supabase Data API and Edge Functions no longer return XHTML on shared domains. Projects that need XHTML responses must enable the Custom Domain add-on. Affected projects notified.

Supabase Read Replicas now scale to five per project on XL or larger compute add-ons, up from two. Smaller compute sizes keep the existing two-replica limit.

Paid plan database billing moves to hourly proration on provisioned disk on 2024-08-26. First 8 GB per project included, then $0.000171 per GB-hour. Free Plan unaffected.

Supabase daily backups switch to physical backups for any project larger than 15 GB, down from the previous threshold. Backups taken this way can no longer be downloaded from the dashboard.

July 2024 developer update previews Launch Week 12 and ships Data API hardening (disable, custom schema), hourly Storage billing, and more Edge Functions included on every plan.

Custom Domain endpoints move from the Let's Encrypt cross-signed chain to the self-signed chain on 2024-09-09. Very old clients such as Android 7.0 and below may lose trust.

Usage data on Supabase invoices and the org usage page now refreshes within one hour instead of 24. Invoices show per-project breakdowns for Compute, Egress, and Realtime Messages.

IPv4, Custom Domain, and Point-in-time Recovery add-ons move to hourly usage-based billing on 2024-08-26. Monthly prices are unchanged. No more upfront charges or prorated credits.

Storage Size billing moves to hourly proration on 2024-08-26. Prices and quotas are unchanged. Short-lived projects and Branching users see lower bills. No action required.

June 2024 developer update: Edge Runtime Inspector for CLI debugging, view and abort running queries in Studio SQL Editor, and log drains via the ELK stack integration.

Edge Functions usage-based billing is removed. Free Plan includes 25 functions, Pro 500, Team 1000, Enterprise unlimited. No extra charges for paid plans that exceed previous limits.

On 2024-07-26, Supabase removes Developer and Read-Only role access to GitHub and Vercel integration management at the organization level. Existing integrations keep working.

From June 24, 2024, paused Free Plan Supabase projects are restorable for 90 days. Projects paused before that date have until September 22, 2024. Paid plans are unaffected.

April 2024 Developer Updates: Supabase reaches General Availability, plus Edge Functions AI model support, Auth anonymous sign-ins, Storage S3 protocol, and Security and Performance Advisors.

March 2024 Platform Updates: higher Supavisor client connection limits, a conversational AI assistant in the SQL Editor, port 6543 transaction-mode only, and v2 platform architecture migration.

Supavisor client connection limits double or more on Small (400), Medium (600), Large (800), and XL (1,000) compute instances. Pricing is unchanged and the limits apply automatically.

Supabase Platform v2 architecture rolls out to Free Plan projects from March 20, 2024, unbundling Storage, Realtime, and the pooler. Existing projects migrate gradually with email notice.

February 2024 Platform Updates: Matryoshka embeddings for vector search, framework Connect snippets in Studio, PostgREST 12 aggregate functions, and an official Supabase Terraform provider.

Paid Supabase organizations can now pick a larger compute size when creating a project, skipping the previous Micro-then-upgrade flow. Up- and downgrades remain available.

January 2024 Platform Updates: Supavisor replaces PgBouncer for pooling, direct connections move to IPv6 with an IPv4 add-on available, plus Studio table-editor and email-template enhancements.

Paid Supabase projects can now enable an IPv4 add-on for direct database connections at $4 per month. Projects using Supavisor or supporting IPv6 do not need it.

From January 24, 2024, Supavisor enforces project Network Restrictions. Existing restrictions propagate automatically; projects without restrictions are unaffected.

Launch Week X recap: Studio AI Assistant and user impersonation, Edge Functions Node and npm support, Supabase Branching, Auth Identity Linking and Hooks, and Read Replicas.

Supavisor 1.1.6 fixes a bug that caused prepared statements to fail when using session mode. No action required.

Supavisor 1.1.5 starts pools with 10 connections and grows up to the tenant pool size, preventing over-allocation of Postgres max_connections during PgBouncer migrations.

Supavisor v1.1.2 adds an allow_list field on tenants for CIDR-based network restrictions and a configurable client_heartbeat_interval to detect dead client connections.

Supabase Platform lowers the daily physical-backup threshold to 40 GB. Restores work as before, but backups taken this way are no longer downloadable from the dashboard.