Supabase Unified Logs Puts Every Service in One Debugging Stream.

Supabase is consolidating one of the messier parts of running a modern backend. Unified Logs, now in open beta, brings events from the platform’s database, authentication, storage and networking services into a single, chronological stream.

Previously, debugging a request could require moving between separate log pages for each service, then trying to reconstruct what happened. According to the company’s LinkedIn announcement, the new interface combines logs from the API gateway, Postgres, Auth, Storage, PostgREST, Realtime and connection poolers. Events appear in one table, with the newest entries first.

That sounds like a straightforward interface change, but it addresses a common operational problem for small teams. A failed login, slow database query or broken file upload can cross several services. When each component maintains a separate view, finding the point of failure takes longer and often demands more knowledge of the underlying architecture.

Unified Logs adds structured filters for log type, severity level, HTTP status, request method and pathname. Developers can also run free-text searches when they know an error message, identifier or other detail but cannot predict which service produced it.

The more consequential capability is request tracing. Selecting a row lets a developer follow the corresponding request through every Supabase service it touched. Instead of manually comparing timestamps and request details across different pages, a team can inspect the path from the gateway to authentication, PostgREST or the database from one place.

The open beta includes four main debugging tools:

• Consolidated events: Logs from seven Supabase service categories appear in one stream.
• Structured and free-text filtering: Teams can narrow results using request metadata or search terms.
• Live tail: New events can be watched as they arrive while reproducing a bug or monitoring a deployment.
• Log Drains: Events can be forwarded to external logging and observability systems.

Live tail should be particularly useful during releases. A developer can start the stream, trigger the affected workflow and watch related events arrive without repeatedly refreshing a page. For businesses running customer-facing automations or applications, that can shorten the gap between a user reporting a problem and the team identifying where it occurred.

Unified Logs also reflects a change beneath Supabase’s log tooling. The company’s changelog says log querying is moving to a ClickHouse-backed Management API endpoint with one unified logs table, rather than separate tables for each source. The older logs.all endpoint is scheduled for removal on September 23, 2026, and users of that API will need to account for the new endpoint’s ClickHouse SQL requirement.

For teams working only in the dashboard, the immediate effect is simpler investigation. For those maintaining custom scripts or monitoring integrations, the API migration is a separate technical consideration and should not be confused with merely receiving the new interface.

Log Drains provide the bridge to existing operational workflows. Supabase has not positioned the unified dashboard as a mandatory replacement for external observability tooling. Instead, a business can investigate events inside Supabase while forwarding them to its own systems for retention, analysis or alerting.

The release arrives as Supabase expands several parts of its developer platform, including more precise realtime subscriptions through Postgres Changes AND filters. For small product teams, Unified Logs is less about adding another service than reducing the operational overhead created by services already in use.

Supabase says Unified Logs is rolling out to all projects during the open beta. Its official blog also lists the release among the company’s product updates. No open-beta end date or plan-specific pricing was provided in the available announcement.

What is Supabase Unified Logs?

Supabase Unified Logs is an open-beta debugging interface that combines logs from the API gateway, Postgres, Auth, Storage, PostgREST, Realtime and connection poolers. It presents those events in one newest-first table and can trace a request across the services it touched.

Which debugging features are included?

The beta supports filtering by log type, level, status, HTTP method and pathname, plus free-text search. It also includes live tail for watching new events, cross-service request tracing and Log Drains for forwarding events to external tooling.

When will Unified Logs be available?

Supabase says the feature is rolling out to all projects during the open beta. The announcement did not provide a completion date, beta end date or plan requirements.