> 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/getting-started/faq.md).

# FAQ

### General

<details>

<summary>How does Pump work?</summary>

Pump is a licensed cloud solutions provider for AWS, GCP, and Azure. When you connect your cloud account, Pump becomes your billing partner and purchases Reserved Instances, Savings Plans, and Committed Use Discounts on your behalf at optimized rates. You receive a single invoice from Pump instead of paying your cloud provider directly. Your infrastructure, workloads, and configurations are untouched.

</details>

<details>

<summary>How is Pump free?</summary>

Pump's  is free because Pump earns revenue as a cloud solutions provider. By consolidating customers under a single billing umbrella, Pump accesses volume-tier pricing from cloud providers. The savings generated by this pricing advantage are split between you and Pump. You pay nothing extra beyond your cloud usage.

</details>

<details>

<summary>Who is Pump for? </summary>

Pump is built for engineering teams, DevOps leads, and finance teams managing cloud infrastructure across AWS, GCP, and Azure. Pump Save has the most impact for organizations spending $5,000 or more per month. Pump View (spend visibility) is available at any spend level.

</details>

<details>

<summary>How long does setup take? </summary>

Most configurations take under five minutes. AWS standalone accounts connect via a one-click CloudFormation stack. GCP and Azure require running a short script in Cloud Shell. AWS Organization accounts require assisted setup with the Pump team.

</details>

<details>

<summary>When will I see savings?</summary>

Most customers see savings within their first week after connecting. Pump begins analyzing your usage immediately and generates commitment recommendations based on your historical data.

</details>

<details>

<summary>What AWS services are supported?</summary>

We work with a variety of AWS services, including:

* Amazon EC2
* Amazon RDS
* Amazon ECS
* Amazon ElastiCache
* AWS Lambda
* Amazon OpenSearch Service
* Amazon SageMaker
* Amazon Redshift
* Amazon DynamoDB
* EC2 Data Transfer
* AWS MediaLive
* Amazon S3
* Amazon CloudWatch

We are the only company that covers such an extensive list of AWS services.

</details>

<details>

<summary>What permissions am I handing off?</summary>

Our permissions are at the billing layer only. We ask you to join our AWS organization and use only IAM roles and permissions to perform all the required cost optimizations and AWS APIs to enable these savings.

We cannot start or stop an instance, and only operate on the billing layer.

</details>

<details>

<summary>Do I risk our actual AWS environment because of Pump?</summary>

Pump would have ZERO ability to modify your environment. There is zero-touch to your infrastructure; thus, there is no chance for any server downtime or interruptions to your developer workflows!

</details>

<details>

<summary>What is the minimum monthly AWS spend needed? Is there a maximum?</summary>

We work with companies with over $5000/mo. spend to all the way to the millions.

</details>

<details>

<summary>What cloud services do you support?</summary>

We support Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. Our platform is designed to optimize, secure, and provide visibility across all these major cloud environments.

</details>

<details>

<summary>I have more questions. Where can I find answers?</summary>

We'd love to help! Email us at <support@pump.co> or text us at 650.468.0297 for the fastest response from the team.

</details>

### Savings

<details>

<summary>We already have Reserved Instances and Savings Plans. Will Pump conflict with them?</summary>

No. Pump detects your existing commitments and optimizes around them. It will not duplicate or conflict with what you already have. As your existing commitments expire, Pump factors the freed capacity into future recommendations.

</details>

<details>

<summary>We have an Enterprise Discount Program (EDP) or Private Pricing Agreement (PPA). Is Pump compatible?</summary>

Yes. Pump works alongside longer term Enterprise Agreements across AWS, GCP and Azure. Pump's commitment management operates on top of these programs. Please contact your account manager for more information.&#x20;

</details>

<details>

<summary>We spend less than $5,000/month. Can we still use Pump?</summary>

Yes. Pump View (dashboards, cost breakdowns, alerts, forecasts) is available on the Base tier at any spend level. Pump Save's commitment management has the most impact at $5,000/month or above, since that is where commitment discounts become meaningful.

</details>

<details>

<summary>How are savings calculated?</summary>

Pump calculates savings 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. The savings number on your dashboard reflects gross savings. Pump's fee (for the Enterprise tier) is billed separately and is not subtracted from the displayed number.

</details>

<details>

<summary>Do commitments belong to me or to Pump?</summary>

All commitments Pump purchases land in your own cloud account. Pump does not pool commitments across customers. If you leave Pump, your commitments remain in your account and run off on their original expiration schedule.

</details>

### Security&#x20;

<details>

<summary>What permissions does Pump need?</summary>

Pump requires read-only access to your billing and usage data. The specific mechanism varies by provider: a cross-account IAM role for AWS, OAuth consent plus a per-project service account for GCP, and a service principal for Azure. Pump never accesses your application data, source code, infrastructure configurations, secrets, or logs. See the Security and Trust page for a full breakdown.

</details>

<details>

<summary>Does Pump modify my infrastructure?</summary>

No. Pump cannot create, modify, start, stop, or terminate any cloud resource. The only write action Pump performs is purchasing commitments (Reserved Instances, Savings Plans, Committed Use Discounts) when you enable Autopilot, and only after you explicitly authorize billing partner access.

</details>

<details>

<summary>Is Pump SOC 2 certified?</summary>

Yes. Pump is SOC 2 Type II certified. Audit reports are available on request. Contact your account team or reach out through [support.pump.co](https://support.pump.co/).

</details>

<details>

<summary>Does Pump store my cloud credentials?</summary>

No. For AWS, Pump assumes a cross-account IAM role using temporary STS tokens. For GCP, OAuth tokens handle project discovery and per-project access is granted to a Pump-managed service account. For Azure, Pump authenticates via a service principal using OAuth2 client credentials. For third-party integrations, API keys are stored encrypted and used only for pulling usage data.

</details>

### Billing&#x20;

<details>

<summary>How does Pump's billing work?</summary>

Pump acts as a licensed cloud solutions provider. When you join Pump, your cloud billing routes through Pump. You receive a separate invoice from Pump for each connected cloud provider. Invoices are published on the 3rd of each month for the prior month's usage. Payment terms are net 7.

</details>

<details>

<summary>Do I still pay my cloud provider directly?</summary>

No. Once connected, Pump handles your cloud billing. You pay Pump, and Pump pays your cloud provider on your behalf.

</details>

<details>

<summary>We have cloud credits. Does Pump work with credits?</summary>

Yes. Pump generally onboards customers whose credits are near exhaustion or already used. If you have a significant credit balance remaining, reach out to the Pump team to discuss timing before connecting your account.

</details>

<details>

<summary>What payment methods does Pump accept?</summary>

Pump accepts credit card, ACH (bank transfer), and wire transfer. Payment methods are managed from Settings > Billing.

</details>

### Offboarding

<details>

<summary>Can I leave Pump at any time?</summary>

Yes. There are no contracts or lock-in periods. You can disconnect from Pump whenever you want.

</details>

<details>

<summary>What happens to my commitments if I leave?</summary>

Existing commitments (Reserved Instances, Savings Plans, Committed Use Discounts) remain in your cloud account and run off naturally on their original expiration schedule. Nothing is canceled early. Your cloud resources, configurations, and data are unaffected.

</details>

<details>

<summary>How do I offboard?</summary>

Contact Pump support at [support.pump.co](https://support.pump.co/). Your billing reverts to direct (you pay your cloud provider instead of Pump), and you can delete the Pump IAM roles, service principals, or IAM grants from your cloud account at any time.

</details>


---

# 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/getting-started/faq.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.