# Manage Logs usage

Logs pricing is being rolled out. Quotas and rates on this page are confirmed but billing enforcement is not yet live. This page will be updated when the rollout is complete.

Logs usage is metered on two SKUs:

- **Logs Ingest** — the total GB of log data Supabase ingests across all your project's services (Postgres, API gateway, Auth, Storage, Realtime, Edge Functions, etc.) during the billing cycle.
- **Logs Query** — the total GB of log data scanned when you read logs via the Studio UI, the Management API, the CLI, or any other interface.

Each plan includes a free quota for both. Usage beyond the quota is billed per GB.

| SKU         | Included (per month) | Over-Usage (Pro, Team)         |
| ----------- | -------------------- | ------------------------------ |
| Logs Ingest | 5 GB                 |  per GB  |
| Logs Query  | 1,000 GB             |  per GB |
| Enterprise  | Custom               | Custom                         |

For full billing details, invoice examples, and optimization tips, see the per-SKU pages:

- [Manage Logs Ingest usage](/docs/guides/platform/manage-your-usage/logs-ingest)
- [Manage Logs Query usage](/docs/guides/platform/manage-your-usage/logs-query)

## Logs vs log drains

[Log Drains](/docs/guides/platform/manage-your-usage/log-drains) stream logs out of Supabase to external destinations (Datadog, Better Stack, your own S3 bucket, etc.) and are billed separately on drain hours and events. Draining logs does not replace or reduce Logs Ingest charges — ingest is metered when Supabase processes your logs, drains are metered when Supabase streams them out. These are separate billing primitives, not overlapping charges.