> 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/how-pump-save-works.md).

# How Pump Save Works

## Pump Save

Pump Save reduces your cloud spend across AWS, GCP, and Azure. It combines automated commitment purchasing with infrastructure-level recommendations to capture savings at multiple layers of your cloud bill.

All savings mechanisms work together. They target different types of waste and complement each other rather than competing. 

### How Pump Save reduces your costs

Pump Save works across three areas:

1. **Save > Commitments (AWS)** provides a full commitment lifecycle for AWS accounts: usage analysis, purchase execution, utilization and coverage tracking, forward planning, and renewal management. Our account team works with you to determine how purchases are reviewed and executed.
2. **Save > Commitments (GCP, Azure)** generates commitment recommendations based on your usage patterns. You review each recommendation and decide whether to proceed.
3. **Save > Infrastructure (AWS)** analyzes your running AWS resources and identifies idle, oversized, or underutilized infrastructure. You review each recommendation and apply changes yourself using the provided commands. No infrastructure changes are made automatically.

All commitments are purchased in your own cloud account. Pump does not pool commitments across customers.

Both are available today. Two additional mechanisms are coming soon:

| Mechanism               | What it does                                                                                        | Status                 |
| ----------------------- | --------------------------------------------------------------------------------------------------- | ---------------------- |
| Save > Commitments      | Full commitment lifecycle: analysis, purchasing, tracking, renewal management                       | Available (AWS)        |
| Save > Commitments      | Generates commitment recommendations for review and approval                                        | Available (GCP, Azure) |
| Save > Infrastructure   | Identifies idle/oversized resources with actionable resize, modernization, and termination commands | Available (AWS)        |
| Kubernetes Auto-Scaling | Optimizes pod CPU and memory sizing, recalibrates horizontal scaling                                | Coming soon            |
| Spot Autoscaling        | Automated spot instance management for fault-tolerant workloads                                     | Coming soon            |

### How savings are calculated

Your savings dashboard shows a single number representing how much Pump has saved you. This includes all savings attributed to Pump across active mechanisms, displayed as the difference between what you would have paid at on-demand rates and what you actually paid.

Pump's fee (for the Enterprise tier) is billed separately and is not subtracted from the displayed savings number. Your invoice shows usage, savings, and fees as distinct line items.

### Commitments belong to you

Every commitment Pump purchases lands in your own cloud account. Pump does not pool commitments across customers. If you leave Pump, your existing commitments remain in your account and active until their expiration date. 

### Getting started

To start saving, connect your cloud account and run a savings estimate. No billing commitment is required to see your estimated savings.


---

# 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/how-pump-save-works.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.