> For the complete documentation index, see [llms.txt](https://docs.north.cloud/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.north.cloud/docs/features/visibility/explore-costs.md).

# Explore costs

Learn how to break down your cloud spend over a date range with Explore.

Explore shows your spend over a date range as a chart and a table. You can split your spend by up to five dimensions, filter it to the costs you care about, and view it from monthly down to hourly.

To open Explore, select **Analyze** in the top navigation, then select **Explore**. For how splits, filters, and Sync work across all three tabs, see [Visibility](/docs/features/visibility.md).

{% hint style="info" %}
To include SaaS spend from a connected Cost Loop, use the **Cost loops** control at the top right. See [Cost Loops](/docs/features/cost-loops.md).
{% endhint %}

<figure><img src="https://1793025303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeLw7hj1pxE38VmG1sYVW%2Fuploads%2FvPa9Jb9i5FXDVwkGKlXH%2FScreenshot%202026-10-07%20at%204.36.31%E2%80%AFPM.png?alt=media&amp;token=93a3f216-442b-40a6-913f-c08ff0e19c22" alt="The Explore tab showing monthly spend split by service and region and filtered by pricing term, with a stacked bar chart and a table of costs split by service and region."><figcaption></figcaption></figure>

## Setting the Date Range and Granularity

Use the controls above the chart to set the granularity, the date range, and the cost basis. The date range presets change with the granularity. Hourly views show Unblended cost.

The longest date range depends on the granularity:

* Hourly: 7 days.
* Daily: 90 days.
* Monthly: 12 months.

## Reading the Chart

The Explore chart shows your spend for each period as stacked bars, with one series for each combination of split values. Use **Display top** dropdown to choose how many series to show. Spend from the remaining series is grouped under **Other**.

## Highest Cost and Top Variant Products

The two cards under the chart show the top three entries for:

* **Highest Cost.** The chart series with the most spend in the date range.
* **Top Variant Products.** The products with the largest increase in daily spend in a given day, within the date range.

## Using Presets

Use a preset for a common Explore view. On AWS accounts, open **Filters** and expand **Presets**:

* **Regions and Accounts.** Daily spend by linked account and region.
* **Purchase type per service.** Daily spend by purchase type and service.

## Exporting Your Data

Click **Export** at the top right of the Explore chart to download the data as JSON or XLSX.

## Limitations

* **Hourly granularity.** Hourly views are available for AWS and GCP accounts. Azure accounts do not have hourly views.


---

# 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.north.cloud/docs/features/visibility/explore-costs.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.
