For the complete documentation index, see llms.txt. This page is also available as Markdown.

Introduction

Pump is a cloud cost optimization platform that helps companies reduce their AWS, GCP, and Azure spend! We combine AI-driven commitment management, infrastructure recommendations, real-time cost visibility, and cloud security scanning into a single tool that takes less than 10 minutes to set up.

Pump is free to use. How are we free, you may ask? We earn revenue through our cloud providers, not from your savings. Unlike our competitors, we don't take a cut of what you save, so every dollar we help you reclaim goes straight back to your bottom line.

Whether you're a startup spending $5K a month on cloud or an enterprise managing $500K+ across multiple providers, Pump gives your engineering and finance teams the visibility, automation, and savings they need to keep cloud costs under control.

Who Pump is for

Pump is built for engineering teams, DevOps leads, and finance teams managing cloud infrastructure. It works best for organizations spending $5,000 or more per month across any combination of AWS, GCP, and Azure.

What Pump does

Pump has three products. Each works independently, and they complement each other when used together.

Product
What it does

Pump Save

Automates cloud cost optimization through commitment management and infrastructure recommendations. Handles RI/SP/CUD purchasing, tracks utilization, and surfaces right-sizing opportunities.

Pump View

Real-time spend observability. Dashboards, cost breakdowns by service, account, region, and tag. Budgets, alerts, end-of-month forecasts, and reports.

Pump Secure

Vulnerability scanning, compliance monitoring, and automated pentesting. Surfaces actionable security findings with severity ratings.

Supported cloud providers

Cloud
Save
View
Secure

AWS

Full support

Full support

Full support

GCP

Full support

Full support

Coming soon

Azure

Full support

Full support

Coming soon

How Pump accesses your data

Pump requests read-only access to your billing and usage data. The specific mechanism varies by provider:

Provider
Access method
What Pump reads

AWS

Cross-account IAM role (deployed via CloudFormation)

Cost Explorer, Cost and Usage Reports, resource inventory (EC2, RDS, ElastiCache, Redshift, OpenSearch), Compute Optimizer

GCP

OAuth consent + per-project service account

BigQuery billing export, project metadata, Cloud Billing account data

Azure

Service principal (app registration + client secret)

Cost Management reports, Consumption usage details, resource groups, billing profiles

The only write permissions Pump uses are for purchasing commitments (RIs, Savings Plans, CUDs) on your behalf, and only when you explicitly enable that capability.

Last updated

Was this helpful?