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

# FinOps

> The cost command center — spend breakdown, chargeback, waste, budgets and caps, and a spend forecast across every gateway.

## What this is for

**FinOps** is Guardway's cost command center. It rolls up estimated USD spend across every gateway and pivots it by team, API key, provider and model — so you can answer "where is the bill coming from", charge it back, find waste, set caps, and forecast the month without pulling a finance export. It replaces the old Dashboard **Spend** view; find it in the left nav at **FinOps**.

Spend figures are **estimates** from hourly rollups, so they lag real time a little, and they are priced from [Settings → Pricing](/platform/settings/pricing). Requests the gateway couldn't price are counted separately.

## Options

At the top of every tab you can set a **time range** — **Month to date** (default), **Last month**, **Last 7 days**, **Last 30 days**, or **Last 90 days** — and filter by **gateway**.

FinOps has six tabs:

### Overview

The headline numbers for the selected range: total spend, how it trends over time, and the biggest contributors — a jump-off into the other tabs.

### Breakdown

Spend attributed across your dimensions — by **team**, **API key**, **provider** and **model** — so you can see exactly what each is costing.

### Chargeback

Spend grouped for internal chargeback, with **CSV export** so you can hand finance a per-team (or per-key) cost file.

### Waste

Cost you could remove: **idle** and **over-provisioned** API keys, plus a **Guardrails avoided** panel that estimates the spend your guardrails prevented by blocking or short-circuiting requests.

### Budgets & caps

Every API-key, team and organization budget with its spend so far, editable inline — change a cap on a row or add one with **New cap**. This is the same budget model documented in [Budgets](/platform/budgets); see there for how each budget type resets and what happens when it's hit.

### Forecast

Projections for the selected period: when a budget is on track to be crossed, and the projected month-close spend at the current run rate.

## How to configure

**1. Open FinOps**

Select **FinOps** in the left navigation. It opens on **Overview** for the current month.

**2. Scope the view**

Pick a **time range** and, if you run more than one gateway, the **gateway** filter.

**3. Drill in**

Move through the tabs — **Breakdown** to attribute spend, **Chargeback** to export it, **Waste** to trim it, **Budgets & caps** to cap it, and **Forecast** to project it.

## Permissions

| Action | Token scope |
| - | - |
| Read spend, breakdowns, waste and forecast | **FinOps → Read spend & budgets** (`finops:read`) |
| Add or change a budget or cap | **FinOps → Read spend and change budgets** (`finops:write`) |

The [Claude connector](/platform/claude-connector#spend-and-budgets) reads spend and sets budgets with the same scopes.

## Related

* [Budgets](/platform/budgets) — how each budget type works and the alerts it sends.
* [Usage](/platform/dashboard/usage) — request and token volume for the same traffic.
* [Settings → Pricing](/platform/settings/pricing) — the per-model prices spend is computed from.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.