> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/pump-save/overview-page.md).

# Overview Page

The Savings Dashboard (Overview) is your central view of how much Pump has saved you. It shows total savings, savings over time, and breakdowns by service or account.

### Reading your savings summary

The top of the dashboard displays your headline savings number. This represents the total amount Pump has saved you, calculated as the difference between what you would have paid at on-demand rates and what you actually paid with Pump's commitment management in place.

Key metrics on the dashboard:

| Metric              | What it shows                                                                                   |
| ------------------- | ----------------------------------------------------------------------------------------------- |
| **Commitments**     | Cumulative dollar amount saved since you joined Pump                                            |
| **Past savings**    | Savings through methods outside of Pump's services, such as previously held SPs/RIs and credits |
| **Savings rate**    | Your savings as a percentage of total eligible spend                                            |
| **Saved with Pump** | Savings attributed to Pump in the current billing period                                        |

### Savings over time

The default timeline view shows your savings trend by month. Use this to track whether your savings are growing, stable, or declining as your usage changes.

A declining savings rate may indicate that your workload mix has shifted and your commitments need rebalancing. Review your pending recommendations in Commitments.

### Savings by service and account

The breakdown view lets you see where your savings are concentrated:

| Breakdown        | What it shows                                                                                                                                                    |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **By service**   | Cloud services that generate the most savings, such as EC2, RDS, and Compute Engine.                                                                             |
| **By account**   | Savings distribution across cloud accounts. Use the graph's filter to select accounts.                                                                           |
| **More filters** | <p><strong>Anomalies:</strong> Services with detected spend anomalies.<br><strong>Commitments:</strong> Services with additional commitment recommendations.</p> |

This helps you identify areas where you are well-optimized and areas where additional commitment coverage could capture more savings.

### Understanding the numbers

A few things to keep in mind when reading the dashboard:

**Savings reflect Pump-attributed optimization.** The number includes savings from commitments that Pump recommended and executed, as well as savings from pre-existing commitments that Pump detected and is tracking.

**Pump's fee is billed separately.** The savings number on the dashboard is gross savings. If you are on the Enterprise tier, your Pump fee appears as a separate line item on your invoice, not as a deduction from savings.

**Infrastructure Recommendations savings are tracked separately.** If you apply an Infrastructure Recommendation (for example, downsizing an oversized EC2 instance), the resulting cost reduction appears in your overall cloud bill but is not rolled into the Commitment Planner savings number on this dashboard. You can view Infrastructure Recommendation impact on the Recommendations page.

### Data freshness

Savings data refreshes as your cloud provider processes billing data. For most providers, this means a delay of up to 24 hours for the most recent data point. Historical data for the current month may adjust slightly as the cloud provider finalizes billing at month-end.

When you first connect, Pump backfills historical data so you can see your cost baseline. Backfill depth varies by provider:

| Provider | Backfill depth           |
| -------- | ------------------------ |
| AWS      | Up to 12 months          |
| GCP      | 7 days (routine refresh) |
| Azure    | Up to 90 days            |


---

# 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://help.pump.co/pump-save/overview-page.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.