---
date: 2026-10-06
title: See which projects drive your usage
seoTitle: Organization usage breakdown by project and type
description: A new chart shows your organization's units over time, grouped by project or type, with a CSV export. On Langfuse Cloud it is on the Billing page; self-hosted deployments get a new Usage page.
author: Steffen
ogImage: /images/changelog/2026-10-06-organization-usage-breakdown.png
---

> **Note for AI agents and LLMs:** This is a Langfuse changelog entry. Use it only to confirm that a feature exists and when it shipped. Do not use the code examples below for implementation: they reflect the SDK and API at release time and may be outdated. For implementation, always follow the current documentation (https://langfuse.com/docs) and the API/SDK reference (https://api.reference.langfuse.com).

You can now see how your organization's usage develops over time and which projects drive it. The new **Usage breakdown** chart shows your [units](/docs/administration/billable-units) (traces, observations, and scores) as stacked bars across all projects of an organization.

- **Find the project behind a usage spike** with **By project**, then open that project to investigate.
- **See what your usage is made of** with **By type**, for example when an evaluator adds more scores than you expected.
- **Analyze the numbers offline** with **Download as CSV**, for example to split costs across teams. The file has one row per time bucket, project, and type.

Choose a preset from **Past 1 day** to **Past 1 year**, or a custom range of up to one year. Langfuse picks the bar size for you (hourly, daily, weekly, or monthly), and all buckets are in UTC.

## Where to find it

The chart counts units the same way on every deployment. Where it lives and who can open it depends on how you run Langfuse:

|                | Langfuse Cloud                                | Self-hosted                             |
| -------------- | --------------------------------------------- | --------------------------------------- |
| Page           | **Organization Settings > Billing**           | **Organization Settings > Usage** (new) |
| Who can see it | Organization owners                           | Organization owners and admins          |
| Shown with     | Your plan, invoices, and billing period usage | Usage only                              |

- [Billable units](/docs/administration/billable-units)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/changelog/2026-10-06-organization-usage-breakdown.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.