> 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/home/welcome-to-pump.md). # Welcome to Pump! The fastest way to cut your cloud bill - without touching your infrastructure. Pump is a cloud cost optimization platform that combines AI-driven commitment management, infrastructure recommendations, real-time cost visibility, and security across AWS, GCP, and Azure. ### How Pump Works - In 30 Seconds Pump sits between you and your cloud provider as an optimization and billing layer. Here's the short version: 1. **Connect Your Cloud:** Link your AWS, GCP, or Azure accounts. Pump starts analyzing immediately, no agents to install, no infrastructure changes, no engineering lift required. 2. **Savings, Visibility, Intelligence:** View all your cloud spend in one place. Pump automatically flags cost anomalies and security gaps while covering baseline savings through AI-driven commitment purchasing and group buying power. 3. **Optimization & Confidence:** Track savings over time, keep forecasts and compliance accurate, and stay audit-ready with continuous security posture monitoring. Pump optimizes in the background so your team can focus on building. ### Still have questions? Reach out to our team at - we typically respond within a few hours! --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://help.pump.co/home/welcome-to-pump.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.