---
slug: logs-usage-based-pricing
published: 2026-09-25
change_type: new-feature
affected_products:
  - Observability
page: https://supabase.com/changelog/logs-usage-based-pricing
---

# Logs usage-based pricing

When you run a backend on Supabase, we instrument it for you — logs come out of the box so you can monitor your services and debug issues without standing up separate infrastructure. We're continuing to invest in them. We're also announcing usage-based pricing early, because we'd rather give impacted projects time to adjust than hand anyone an unexpected bill. More than 90% of projects are within the included limits and won't be affected; for those that are, the grace period through early 2027 gives you time to understand and tune your usage before enforcement begins.

## Background

We've been working for years to bring meaningful observability to Supabase developers — shipping [Unified Logs](https://supabase.com/blog/unified-logs-open-beta), [client trace integration](https://supabase.com/blog/connect-client-traces-to-your-logs), [Log Drains](https://supabase.com/blog/log-drains-now-available-on-pro), [Observability Auto-Pilot](https://supabase.com/changelog/50403-observability-autopilot), and [Health Check Advisors](https://supabase.com/changelog/50577-health-check-advisors), among other things. We'll keep going — more ways to surface logs meaningfully, more tools to help you monitor and debug, with or without an agent in the loop.

But as we've scaled to millions of projects, the infrastructure behind logs has scaled with us. Usage-based pricing is how we make sure we can keep building, in a way that's fair for everyone.

## Usage-based pricing

That said, there are workloads where logs will scale with usage — and at platform scale, that needs to be priced fairly. We're introducing usage-based pricing for logs ingest (the volume of log data generated by your services) and a quota that scales with ingest for log query (the volume scanned when reading logs).

This is a soft launch: usage is now metered and visible in your project's usage dashboard, but limits are not yet enforced. A grace period runs through early 2027, giving you time to understand your usage before billing begins. More than 90% of projects are within the included limits and won't be impacted.

## What we've done to control log volume

A significant part of this work has been changing default logging behavior across the Supabase stack, and giving you more control over your own:

- We've shipped fleet-wide changes to reduce noisy defaults — for example, disabling connection logging (`log_connections`) across most plans, which alone cut tens of millions of log rows per hour fleet-wide.
- Postgres log settings are configurable and often the biggest lever for teams running heavy query workloads. Settings like `log_statement`, `log_min_duration_statement`, and `log_min_messages` can dramatically reduce volume when tuned. See [Postgres log settings](https://supabase.com/docs/guides/database/custom-postgres-config#superuser-settings) and the [log field reference](https://supabase.com/docs/guides/observability/log-field-reference) to understand what each source captures.
- We've published guides to help you understand your usage and take action: [Manage Logs Ingest](https://supabase.com/docs/guides/platform/manage-your-usage/logs-ingest) and [Manage Logs Query](https://supabase.com/docs/guides/platform/manage-your-usage/logs-query).

We'll keep adding controls. The goal is that the defaults are right for most projects, and that teams who need to go further have the tools to do it.

## What's coming to Studio

Starting soon, your project's usage dashboard will show log ingest and query meters with an "Upcoming" label. If you approach your limits during the grace period, you'll see a warning in Supabase Studio — these are informational only, not enforcement actions.

## Why we built this

Supabase has a healthy free tier, and we're committed to keeping it that way. Usage-based pricing makes that possible: when infrastructure costs reflect actual use, high-volume projects pay their share rather than that cost being spread across the fleet. It also lets us keep finding more meaningful ways to surface logs — better tools to understand, access, and act on what they're telling you, with or without an agent in the loop — in a way that's sustainable and fair for everyone, whether you're a hobbyist, a growing startup, or a large enterprise.

## Share your feedback

This is a soft launch and we're actively seeking input. If you're notified about your usage during the grace period — or you have thoughts on pricing, limits, or the tooling — we'd love to hear from you. Visit our GitHub Discussion to share feedback directly with the team.