AI Devtools Radar

Supabase

Backend platformssupabase.com7 published changes

2 sources under watch

Change timeline

otherhigh

PostgreSQL 15.19 and 17.11 minor releases with potential breaking changes for ltree, pgcrypto, btree_gist, and custom operators

Supabase customers using PostgreSQL 15.x or 17.x may need to take action to ensure compatibility with ltree, pgcrypto, btree_gist extensions or custom operators after the upgrade

Evidence
+PostgreSQL 15.19 / 17.11 minor release — action may be required for ltree, pgcrypto, btree_gist, and custom operators

supabase.com

pricing

Log Ingestion overage pricing set at $0.50 per GB

Users exceeding included log ingestion quota (20 GB) will be charged $0.50 per additional GB.

Evidence
+20 GB includedthen $0.50 per GB

supabase.com · also seen at 1 more source

featurehigh

Database Replication feature renamed to Pipelines

Users of Supabase's database replication feature will need to update their mental model and documentation references as the feature is now called Pipelines. This may affect product navigation, documentation, and user communication.

Evidence
+Database Replication is now Pipelines

supabase.com · also seen at 1 more source

other

Fixed daily backups occasionally skipped due to scheduling timeout

Users with Supabase databases will have more reliable daily backup completion, reducing the risk of missed backups due to timeout issues.

Evidence
+Fixed daily backups occasionally skipped due to a scheduling timeout

supabase.com · also seen at 1 more source

deprecationhigh

Extension version pinning deprecated: from 2026-08-05 explicit versions in create extension are ignored

Statements like create extension pgvector version '0.7.0' will install the project's default version and emit a warning starting 2026-08-05; a future release will reject them with an error. Migration scripts and IaC that pin Postgres extension versions on Supabase need updating.

Evidence
+Starting 2026-08-05, specifying an explicit version when creating or updating a Postgres extension on Supabase is deprecated. [...] the extension installs the default version on your project's Postgres instance, and the statement emits a warning. In a future release, announced separately in advance, these statements will be rejected with an error instead. [...] Pinning versions is now reserved for platform operations.

supabase.com

feature

Realtime Broadcast now supports binary payloads over WebSockets, REST API, and database

Developers can now send and receive binary payloads (bytea) through Realtime Broadcast, reducing JSON overhead for sensor streams and image frames.

Evidence
+Supabase Realtime Broadcast now sends and receives binary payloads (bytea) over WebSockets, the REST API, and the database, cutting JSON overhead for sensor streams and image frames.

supabase.com · also seen at 1 more source

apihigh

logs.all Management API endpoint being deprecated and replaced with new ClickHouse-backed logs endpoint

Users querying the logs.all endpoint must migrate to the new logs endpoint and convert queries to ClickHouse SQL dialect before September 23, 2026. This affects scripts, integrations, and tooling calling this endpoint directly.

Evidence
+The logs.all Management API endpoint is being removed on 23rd September 2026 (Wednesday), two months from this announcement. Log querying moves to a new ClickHouse-backed logs endpoint. The new endpoint accepts ClickHouse SQL only.

supabase.com