> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud & SaaS Contract Tracker

> Track commitment burn-down against actual spend from any connected cloud or SaaS integration—PPAs, EDPs, cross-service agreements, and marketplace caps.

**Cloud & SaaS Contract Tracker** helps you monitor commitment utilization against real spend. Create contracts for enterprise agreements, PPAs, EDPs, or scoped provider and SaaS spend, then watch burn-down progress over time with forecasts and period-by-period summaries.

Spend is pulled from **any integration connected to your organization**—cloud providers (AWS, GCP, Azure) and third-party tools (for example Databricks, Snowflake, and other SaaS billing sources)—using the same dimensions as [Explorer](/inform/explorer). Product services, cost entities, billing entities, and marketplace products all appear in the pickers based on what is flowing into nOps.

## Get started

1. Sign in to [nOps](https://clara.nops.io/dashboard).
2. In the sidebar, open **Operate → Cloud & SaaS Contract Tracker**, or go to [clara.nops.io/contract-tracker](https://clara.nops.io/contract-tracker).
3. Click **Add contract** and walk through the three-step setup wizard.
4. After you save, the burn-down chart loads for your new contract. If you already have contracts, the page opens on your most recently updated one.

<Note>
  Contract Tracker requires the **Operate** entitlement and the **Contract Tracker** permission for your role. If you do not see it in the sidebar, ask your organization administrator.
</Note>

## Key features

### Contract list and switching

When you have one or more contracts, use **Manage Contracts** in the page header to:

* **Search** by contract name, tracking summary, or dates.
* **Switch** the active contract—the chart and summary update for your selection.
* **Copy link** to share a direct URL to the current contract (`/contract-tracker/{id}`).
* **Create new** to start another contract without leaving the page.

Each row shows the contract name, what it tracks, its date range, and total commitment.

### Creating a contract (three-step wizard)

Click **Add contract** to open the wizard.

#### Step 1 — Track

Define what spend counts toward the commitment:

* **Contract name** — A display name for cards and charts (for example, *AWS Enterprise Agreement 2026*).
* **Track by** — How spend is grouped:

| Mode                | Use when                                                                                                                                                                        |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Product service** | The commitment applies to specific product or service lines (for example EC2, S3, Databricks, or Snowflake).                                                                    |
| **Cost entity**     | The commitment applies to selected billing cost entities.                                                                                                                       |
| **Cross service**   | The commitment spans billing entities, marketplace products, cost entity legal names, and product services in one agreement—useful for multi-provider or enterprise-wide deals. |

Select at least one tracked value for your chosen mode. For **Cross service**, pick from:

* **Cost entity** (billing entities such as AWS or AWS Marketplace)
* **Marketplace entities** (individual AWS Marketplace products)
* **Cost entity legal name**
* **Product service**

<Info>
  If you select **AWS Marketplace** as a billing entity, individual marketplace product pickers are disabled—the marketplace cap (see Step 2) applies to total AWS Marketplace spend instead.
</Info>

#### Step 2 — Duration

Set the contract window and commitment amounts:

* **Period** — How commitments are divided: **Monthly**, **Quarterly**, or **Annually**.
* **Start date** and **End date** — The full contract term.
* **Discount percentage** — For **Cross service** contracts only (for example, your EDP discount).
* **Marketplace cap allocation** — Shown when AWS Marketplace is in scope. Set the percentage of each period's commitment that can apply to Marketplace spend before the cap is exhausted (default 50%).
* **Commitments** — Enter the dollar commitment for each period in the contract (one row per month, quarter, or year, depending on **Period**).

#### Step 3 — Review

Confirm name, tracking mode, dates, discount, marketplace cap (if any), tracked values, and per-period commitments. Click **Create contract** to save.

### Burn-down chart

The main chart shows how actual spend compares to your commitment over the contract term:

* **Stacked bars** — Monthly spend broken out by tracked entity (product service, cost entity, etc.).
* **Monthly Target** (dashed line) — The prorated commitment target for each month.
* **Remaining commitment** (line) — How much commitment is left at each point in time.
* **Forecast** — Future months with projected spend appear with a lighter, dashed bar style so you can see where you are headed before the period ends.

The chart header also shows **Actual**, **Commitment**, and **Variance** for a quick read on whether you are ahead or behind.

### Period summary cards

Below the chart, summary cards break the contract into commitment periods (months, quarters, or years). Each card shows:

* **Actual spend** vs. **target** for that period
* **Variance** and **On Track** / **Behind** status
* A progress indicator for the period

Use these cards to spot which half of a multi-year agreement is running hot or cold.

### Editing, deleting, and sharing

* **Edit** — Open **Manage Contracts**, then use the pencil icon on a row you are allowed to change. The same three-step wizard opens with existing values filled in.
* **Delete** — Use the trash icon on an allowed row. Deletion is permanent and removes the contract and its burn-down history from your organization.
* **Share** — Use **Copy link** in **Manage Contracts** so teammates can open the same contract directly.

Only the contract **creator** or an organization **administrator** can edit or delete a contract. Everyone with access can view contracts and copy links.

## FAQs

<AccordionGroup>
  <Accordion title="What spend does Contract Tracker include?">
    Contract Tracker uses cost and usage from **every integration connected to your organization**—the same unified data and dimensions you see in Explorer. That includes major cloud providers (AWS, GCP, Azure) and third-party SaaS billing sources (for example Databricks and Snowflake) once they are onboarded in [Integrations](/platform/integrations). Depending on how you configure each contract, tracked spend can be scoped by product service, cost entity, billing entity, or marketplace product. It does not replace provider-native commitment consoles; it gives you a unified burn-down against the commitments you define in nOps.
  </Accordion>

  <Accordion title="When should I use Product service vs. Cost entity vs. Cross service?">
    Use **Product service** when the agreement is scoped to specific services or SKUs (cloud or SaaS). Use **Cost entity** when billing entities define the boundary (for example, a payer account or vendor entity). Use **Cross service** for enterprise-wide deals that combine multiple billing entities, marketplace products, legal entities, and services—with optional EDP discount and marketplace cap settings where AWS Marketplace is in scope.
  </Accordion>

  <Accordion title="What is the marketplace cap allocation?">
    For cross-service contracts that include AWS Marketplace, the cap limits how much of each period's commitment can be consumed by Marketplace spend. If you select **AWS Marketplace** as a billing entity, the cap applies to all Marketplace spend—you do not need to pick individual marketplace products. If you pick specific marketplace products instead, you can still set the cap percentage per period.
  </Accordion>

  <Accordion title="How is the forecast calculated?">
    Future months on the chart use projected spend based on your historical burn rate in the contract. Forecast bars are styled differently from actuals so you can distinguish recorded spend from projections.
  </Accordion>

  <Accordion title="Who can create or change contracts?">
    Any user with Contract Tracker access can create contracts and view burn-down data. Only the user who created a contract or an organization administrator can edit or delete it.
  </Accordion>

  <Accordion title="Why does the page open on a specific contract automatically?">
    If you have saved contracts, visiting `/contract-tracker` redirects to your most recently **updated** contract, or the one in the URL. Use **Manage Contracts** to switch, or share a link that includes the contract ID (`/contract-tracker/{id}`).
  </Accordion>

  <Accordion title="Do I need integrations connected first?">
    Yes. Connect the cloud accounts or third-party tools whose spend you want to track via [Integrations](/platform/integrations). Once billing data is flowing into nOps, the same dimensions you use in Explorer appear when you build a contract. If a vendor or service does not show up in the dimension pickers, confirm that integration is active and has recent data in Explorer.
  </Accordion>
</AccordionGroup>

## Related

* [Explorer](/inform/explorer) — analyze spend by the same dimensions used in contract tracking
* [Budgets](/operate/budgets) — set periodic spend targets and threshold alerts from Explorer reports
* [Business Unit Economics](/operate/business-unit-economics) — tie cloud spend to business metrics like customers or seats
* [Dashboard](/platform/dashboard) — organization overview and cloud spend summary