Supabase Meters Logs Ingest, Delays the Bill Until 2027

Supabase said Sept. 25, 2026, that Logs is moving to usage-based pricing, starting by metering ingest volume across every plan (Supabase changelog, Sept. 25, 2026). Usage is now visible per project in the dashboard, but the company says it won’t enforce limits or start billing until early 2027, and that more than 90% of existing projects already sit inside the included quota.

What the meter actually charges

Supabase’s usage docs spell out the numbers the changelog post leaves out. Logs ingest carries a free monthly quota of 1 GB on the Free plan and 20 GB on Pro, Team and Enterprise; once billing starts, anything past that costs $0.50 per GB. Logs query isn’t billed on its own. Instead, each project gets a query allowance that scales with ingest, 100 GB of query capacity for every 1 GB ingested, so a noisier logging setup also buys itself more room to search its own history.

Enforcement differs by plan, too. Free-tier projects and any paid project with a spend cap enabled get a notification and a Fair Use Policy grace period if they exceed quota. Paid projects with spend caps off are billed for the overage automatically once the grace period through early 2027 ends.

The pattern behind the announcement

This is the third time in three months Supabase has touched the economics of Logs. It turned off default Postgres connection logging with no opt-in on July 9, then made its Pipelines replication tool bill hourly even while paused when it opened to public alpha on July 23. On Sept. 23, it retired the logs.all Management API endpoint that older MCP tooling relied on for pulling logs at all.

Taken separately, each looks like platform maintenance. Taken together, they trace logging’s move from an included convenience toward a metered product with its own API surface and its own bill. Supabase’s framing here, that 90% of projects won’t feel it, is the same reassurance that preceded Vercel’s CPU-minute billing complaints earlier this month: the number describes today’s traffic, not what a team’s logging volume looks like once an agent workflow or a debugging spree starts writing to it by default.

Key Takeaways

• Supabase’s Sept. 25, 2026 changelog moves Logs to usage-based pricing; ingest volume is now metered and visible per project.
• Included ingest is 1 GB a month on Free and 20 GB on Pro, Team and Enterprise; overage runs $0.50 per GB once billing starts.
• Logs query isn’t billed directly. Each project gets a query allowance of 100 GB for every 1 GB ingested.
• No enforcement or billing begins until early 2027, and Supabase says more than 90% of current projects already sit within the included limits.