> 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/cost-loops.md).

# Cost Loops

Learn what a Cost Loop is, which SaaS providers North supports today, and which ones are coming.

A Cost Loop brings SaaS spend into North alongside your cloud accounts. Your warehouse bill, your AI API bill, and your observability bill then sit in the same views as your AWS, Google Cloud, and Azure spend, with the same charts, the same allocation model, and the same filters.

A Cost Loop is read-only. North reads usage and cost from the provider. North does not change anything in your provider account.

You attach a Cost Loop to an organization that already has a cloud account. Add one at any time.

## Available Today

| Provider  | What it covers                        | How North authenticates |
| --------- | ------------------------------------- | ----------------------- |
| Snowflake | Warehouse compute and storage spend   | RSA key pair            |
| Anthropic | Claude usage                          | API key                 |
| OpenAI    | Organization-wide API usage and spend | Admin API key           |
| Datadog   | Observability and APM spend           | Service Access Token    |

Review the setup guide to get started on each one:

{% content-ref url="/pages/KnkHzPqzhm5D5uJZI7C9" %}
[Snowflake](/docs/features/cost-loops/snowflake.md)
{% endcontent-ref %}

{% content-ref url="/pages/q8oZeYUVEuhOMcwwKxy8" %}
[Anthropic](/docs/features/cost-loops/anthropic.md)
{% endcontent-ref %}

{% content-ref url="/pages/Xf4a0TANX2ATGXzlwHG7" %}
[OpenAI](/docs/features/cost-loops/openai.md)
{% endcontent-ref %}

{% content-ref url="/pages/6OVAz9P0iPYraLpfyAkI" %}
[Datadog](/docs/features/cost-loops/datadog.md)
{% endcontent-ref %}

## Coming Soon

More providers are on the way.

| Provider      | What it will cover              |
| ------------- | ------------------------------- |
| Databricks    | Lakehouse and jobs spend        |
| MongoDB Atlas | Cluster and data-transfer spend |

## How to Add a Cost Loop

1. Open **Settings**, then **Integrations**.
2. Click **Add accounts**.
3. Under **Cost Loops**, select the provider you want.
4. Follow that provider's setup guide.

## Naming Your Connection

Every Cost Loop asks for a connection name. Choose something you will recognize later. That name is what labels the provider's card on your homepage, and what identifies the connection when you pick Cost Loops for a Streams view or for Visibility.

## What Cost Loops Do Not Cover

Two limits are worth knowing before you plan around Cost Loops.

**Cost Loops carry no commitments.** North covers cloud spend with Savings Plans, Reserved Instances, and CUDs. None of that applies to a Cost Loop. A Cost Loop reports spend. It does not buy anything against that spend, and Cost Loop spend does not appear in your coverage or your Effective Savings Rate.

**Commitments work on one cloud account at a time.** You can combine a cloud account and several Cost Loops in a single Streams view or Visibility selection. Commitments do not work that way. They operate on one cloud account, so a multi-account view is for reporting rather than for buying coverage.

## Where the Data Appears

Once a Cost Loop is connected, its spend shows up on your homepage, in Streams, and in Visibility, and you can ask Noros about it. The detail available differs by provider.

{% content-ref url="/pages/MOGdLqJ1QntWx8i6nM2I" %}
[Viewing Cost Loop Data](/docs/features/cost-loops/viewing-cost-loop-data.md)
{% endcontent-ref %}


---

# 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/cost-loops.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.