> 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/govern-control-and-governance/budgets/create-budgets.md).

# Create Budgets

## Create a Budget

Creating a budget takes two steps. Step 1 sets what you are budgeting for. Step 2 sets the period and the amounts.

To start, go to **Govern → Budgets** and click **Create Budget**.

### Step 1: Choose what to budget

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FfL8RJJOnWopSz0Pszv6N%2Fimage.png?alt=media&amp;token=a3fd1482-1841-4f5e-aa6f-d2269eddded8" alt=""><figcaption></figcaption></figure>

1. Enter a **Budget Name**.
2. Choose where the costs come from:
   * **Create from Report** builds the budget on a Report you already have. Select the Report.
   * **Create from Scratch** builds a new Report together with the budget. Enter a **Report Name**, then fill in the fields below.
3. Select the **Source**. Choose **Global** to budget across all connected sources, or pick a single provider such as AWS, Azure, GCP, Cloudflare or Claude.
4. Choose **Budget By**. This is the dimension the budget is split by. Each value becomes its own row with its own amount, for example one row per GCP project or per Claude model.

   You can split by the source's own dimensions, or by **Cost Center**, **Virtual Tag** or **Environment**. For Claude, the source dimensions are Account, Caller Identity, Model and Region.

   <\<SS = create-budget-step1-budget-by>>
5. Optional. Under **Show Results Where**, click **Add Rule** to limit which costs count toward the budget.
6. Select the **Cost** type. The default is **Actual Cost**.

### Step 2: Set the period and amounts

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2Fn0nuspuLAIN0Ql9hZry1%2Fimage.png?alt=media&amp;token=50237107-cba6-4a79-8ecf-e36c64f5e2c9" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FP2ae1DvPEAFUonf8c8zR%2Fimage.png?alt=media&amp;token=a33b462d-bd13-4d97-ab1f-5620ec4ca5fb" alt=""><figcaption></figcaption></figure>

1. Set the **Start Date** and **End Date** (month and year). Tick **Use custom time period** to set a custom range.

2. Choose the **Budget Granularity**. This is the length of each budget period, for example Monthly.

   <\<CONFIRM = Budget Granularity options>>

3. Choose the **Budget Type**.
   * **Manual**. You enter every amount yourself.
   * **Auto**. OneLens fills in the amounts from your past cost data.

4. For an Auto budget, choose:

   * **Lookback Period**. How much cost history OneLens uses, for example Last Year.
   * **Auto Budgeting Formula**. How OneLens turns that history into an amount, for example Maximum.

5. Review the **Budget Breakdown** grid. Each row is one value of your Budget By dimension and each column is one period. Click any cell to change its amount. You can edit Auto amounts too.

6. To work on amounts outside OneLens, use **Export** to download the grid and **Import** to load it back.

### Tips

* Start with an Auto budget, then edit the rows you know will change, such as a project you plan to migrate or shut down.
* Split the budget by a dimension that matches ownership, such as Cost Center or project. Budget alerts are then easy to route to the people who own each row.


---

# 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/govern-control-and-governance/budgets/create-budgets.md?ask=<question>&goal=<user_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.
