> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/observe-visibility-and-insights/unit-economics.md).
# Unit Economics
Unit Economics turns your cloud, AI and SaaS cost into a cost per unit that means something to your business, such as cost per customer, per product or per feature.
Go to **Observe → Unit Economics**. The page has three tabs.
| Tab | What you do there |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Datasets | Bring in the business data used to share out cost: your customers or products, how they map to cloud accounts, and usage numbers such as database size |
| Unit Cost Engine | Build an allocation rule. You combine datasets and cost on a canvas, step by step, into one final report |
| Analytics | Explore a published report: cost per unit over time, grouped and filtered the way you need |
### How it fits together
If you work this out in a spreadsheet today, you probably have a few raw sheets, some working sheets built with lookups, and one final sheet you send. Unit Economics follows the same shape:
1. **Datasets** hold the raw inputs.
2. In the **Unit Cost Engine**, contributors (your datasets and cost sources) feed intermediate tables, and the intermediate tables feed one final report.
3. You **publish** the report on a schedule, then read it in **Analytics**, on dashboards, and in workflow alerts.
### Example: database cost per customer
Say you want to share your database bill across customers by how much database space each one uses.
| Where | What you set up |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Datasets | An entity that lists your customers, and a metric with each customer's database size per month |
| Unit Cost Engine | Contributors: the customer entity, the database size metric, and your cloud cost. One intermediate table works out each customer's share of total database size. The final report applies that share to the cost |
| Analytics | Cost per customer by month, shown next to each customer's database size |
### Use the results elsewhere
**Dashboards.** When you add a widget, pick the **Unit Economics** module to show a report next to Cost 360, Kubernetes and Anomaly widgets.
**Workflows.** You can set alerts that export unit economics reports automatically and flag runs that fail.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.onelens.cloud/observe-visibility-and-insights/unit-economics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
