> 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/arctic/getting-started.md).

# Getting Started

## Before You Start

* North analyzes your usage every day and projects the savings available on each of your services. Review them on your homepage under **Available Savings**. For the detail per plan, open the [Commitments](https://app.north.cloud/commitments) page.
* Check [Coverage Plans](/docs/features/arctic/coverage-plans.md) to confirm that the services you want to cover are supported. That page also shows whether each plan is available through Flexbot, Autobot, or both.
* If you have just onboarded onto North, note that it can take a few hours before your usage and coverage data starts showing up on the Commitments page.

## View your Commitments

The Commitments page is your control center for all things related to coverage. It shows your current commitments, the health of those commitments, any commitments that are queued to be purchased, and analytics tied to your coverage.

1. On the Commitments page, select the service for which you want to see your usage and coverage data.
2. On the 'Current Coverage and Projection' section, you can see your spend and coverage charts across various time ranges. Switch between simple and inventory views to see different visualizations of your data.
3. See a list of your current commitments and their health on the 'Commitments Health' section. This includes both commitments held by you as well as North. The list is filterable by date ranges, commitment type, region, whether it is held by North or not, and whether it is underperforming.
4. View any pending and forecasted commitments in the 'Pending & Forecasted' section. This is where you can see any purchases that are queued once you buy coverage through North.
5. See high-level metrics about your coverage in the Analytics section.

The [Commitments](/docs/features/arctic/commitments.md) guide covers each section in detail, including explaining all the metrics listed on this page.

## Turn On Coverage

1. On the Commitments page, click **Adjust Coverage**.
2. Set your coverage target, and set your Auto / Flex split.
3. Select a coverage profile for the Autobot share.
4. Review the simulation's results.
5. Click **Update Policy**, then authorize the configuration.

[Purchasing Coverage](/docs/features/arctic/purchasing-coverage.md) covers every step in detail. It also lists the permissions Autobot needs before it can purchase for you.

## Frequently Asked Questions

### How Are Savings Pods Removed From My Environment?

Savings Pods are the North-managed accounts you add when Flexbot covers part of your spend. North removes them automatically. North can also remove them at your request. You keep full control over these accounts, and you can remove them whenever you need to. The Master Services Agreement applies for non-emergency events.

### Is There Any Concern With Adding North's Accounts to My Environment?

No. Savings Pods are North-managed accounts that distribute commitment discounts into your account. [Managed Savings Pods](/docs/getting-started/security/managed-savings-pods.md) describes the security controls North puts in place.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.north.cloud/docs/features/arctic/getting-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
