# Usage pricing

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Faccount-management%2Forganization-management%2Fusage-and-quota%2Fhow-usage-is-measured.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Faccount-management%2Forganization-management%2Fusage-and-quota%2Fhow-usage-is-measured.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

## How usage is measured[​](#how-usage-is-measured "Direct link to How usage is measured")

Usage is billed in **units**, a universal metric per entity type. **Entity types** break the observability pillars into finer-grained objects, and ingested data flows through TCO pipelines whose [priority](https://coralogix.com/docs/user-guides/account-management/tco-optimizer.md) sets the unit cost. Data that matches no policy is treated as high priority. Usage counts against your [daily unit quota](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/quota-rules.md).

One unit equals $1.50 of usage for logs, metrics, or traces in any pipeline.

Entity types by pillar

| Pillar   | Example entity types            | Description                                                                                                                                                                         |
| -------- | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Logs     | Browser logs, alerts            | Event data from applications or user interactions                                                                                                                                   |
| Metrics  | Metrics                         | Numeric measurements of system performance                                                                                                                                          |
| Traces   | Spans                           | Detailed traces of operations and transactions                                                                                                                                      |
| Binary   | Session recordings, Source maps | Large binary objects, such as recordings or debug files                                                                                                                             |
| Profiles | CPU profiles                    | Continuous profiling data for performance analysis                                                                                                                                  |
| AI       | Olly, Evals, Guardrails         | Per-user AI usage and AI Center evaluations and guardrails, billed in [AI units](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/ai-units-pricing.md) |

Unit rates by pipeline

Logs:

| Pipeline        | Sent data | Units |
| --------------- | --------- | ----- |
| High priority   | 1 GB      | 0.75  |
| Medium priority | 1 GB      | 0.32  |
| Low priority    | 1 GB      | 0.12  |
| Blocked logs    | 1 GB      | 0.08  |

Metrics:

| Pipeline | Sent data | Units |
| -------- | --------- | ----- |
| Metrics  | 30 GB     | 1     |

Traces:

| Pipeline        | Sent data | Units |
| --------------- | --------- | ----- |
| High priority   | 1 GB      | 0.5   |
| Medium priority | 1 GB      | 0.25  |
| Low priority    | 1 GB      | 0.1   |

Infrastructure events are not billed, at any volume.

User-defined datasets

Data routed to [user-defined datasets](https://coralogix.com/docs/user-guides/data-layer/default-dataspace/user-defined-datasets.md) counts against the same daily quota, tracked per dataset and per dataspace. The unit cost follows the TCO priority of the routing policy applied to that dataset, at the standard log rates:

| Pipeline        | Sent data | Units |
| --------------- | --------- | ----- |
| Medium priority | 1 GB      | 0.32  |
| Low priority    | 1 GB      | 0.12  |

**High** and **Block** priorities are available for `default/logs` only. User-defined datasets do not support them.

Dataset-level usage appears on the **User data sent** tab. Group by `Dataset` to see usage per dataset.

To turn ingestion usage into queryable metrics for dashboards and alerts, enable [Data usage metrics](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/data-usage-metrics.md).