> 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/how-we-work-with-cloud-providers/how-pump-works-with-gcp.md). # How Pump Works with GCP This page is for GCP account managers who want to understand how Pump operates within the Google Cloud ecosystem. For customer-facing setup instructions, see [Connecting Your GCP Account](https://help.pump.co/~/revisions/nqQuS4sCqArty7ozYkOl/gcp/getting-started-with-gcp-1). ### Pump's GCP Partner Status | Detail | Value | | --------------- | ---------------------------------------------------------------------------------------------------- | | Program | Google Cloud Partner | | Partner listing | [cloud.google.com/find-a-partner/partner/pump](https://cloud.google.com/find-a-partner/partner/pump) | | Distribution | Ingram Micro | ### How the GCP Relationship Works When a customer joins Pump on GCP, their billing account becomes a sub-account under Pump's solutions provider billing account. This is the standard Google Cloud solutions provider model. Pump consolidates billing across its customer base, enabling volume-tier pricing. The customer's GCP projects, resources, workloads, and configurations remain entirely under the customer's control. #### What changes for the customer | Before Pump | After Pump | | ---------------------------------------- | ----------------------------------------------------------------------------------------------------------- | | Customer pays Google Cloud directly | Customer's billing account is a sub-account under Pump. Customer receives a consolidated invoice from Pump. | | Customer manages their own CUD purchases | Pump manages Committed Use Discount purchases on the customer's behalf (if configured) | #### What does not change The customer retains full ownership and administrative control of their GCP projects. The customer's existing Google Cloud support plan remains active. The customer's AM relationship is unaffected. ### How Connection Works The customer connection flow has three steps: 1. **OAuth consent.** The customer authorizes Pump to list their GCP projects using read-only scopes (`openid`, `userinfo.email`, `userinfo.profile`, `cloudplatformprojects.readonly`). This gives Pump visibility into the customer's project structure, nothing more. 2. **Per-project IAM grant (optional).** The customer runs a script in Cloud Shell that grants Pump's service account limited permissions on specific projects. This enables commitment optimization for those projects. 3. **Billing account join.** The customer's billing account is linked as a sub-account under Pump's solutions provider billing account. This is the step that activates the solutions provider relationship. ### Permissions Pump Receives #### OAuth scopes (all customers) | Scope | Purpose | | ------------------------------------ | ---------------------------- | | `openid` | Authentication | | `userinfo.email`, `userinfo.profile` | User identification | | `cloudplatformprojects.readonly` | List customer's GCP projects | #### Per-project IAM roles (customers who run the setup script) | Role | Purpose | | -------------------------------------- | ----------------------------------------------------------------------- | | `roles/bigquery.resourceAdmin` | Access to billing export data for cost analysis | | `roles/compute.viewer` | Read-only access to compute instance metadata for right-sizing analysis | | `roles/compute.futureReservationAdmin` | CUD purchase execution | These roles are granted to Pump's service account on a per-project basis. The customer controls which projects Pump has access to. ### How Commitments Are Managed Pump analyzes the customer's compute usage patterns and existing CUD portfolio using BigQuery billing export data. It calculates optimal Committed Use Discount purchases based on usage trends and existing coverage. Commitments purchased by Pump are scoped to the customer's own project. Pump does not pool commitments across customers. If a customer leaves Pump, their CUDs remain in their project and run off on their natural expiration schedule. ### Impact on AM Quota Customer spend that flows through Pump still counts toward the GCP AM's quota and attribution. Pump does not take commission from GCP AMs. Pump's solutions provider model is additive to the AM relationship. ### Data Sources Pump Uses | Source | What Pump reads | Purpose | | ----------------------- | --------------------------------------- | ---------------------------------------------- | | BigQuery billing export | Standard and detailed billing data | Cost analysis, dashboards, commitment planning | | Cloud Resource Manager | Project listing and metadata | Multi-project visibility | | Cloud Billing API | Billing account and project enumeration | Account structure mapping | | Compute Engine API | Instance metadata (read-only) | Right-sizing analysis | #### Data backfill On first connection, Pump pulls up to 35 days of historical billing data from BigQuery. Routine refreshes operate on a 7-day rolling window. ### SOC 2 Type II Pump is SOC 2 Type II certified. Audit reports are available on request through . ### Questions? If you have questions about a specific customer's Pump setup or about Pump's GCP partner status, contact . --- # 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/how-we-work-with-cloud-providers/how-pump-works-with-gcp.md?ask=&goal= ``` `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.