Quick Start

This guide walks you through signing up for Pump, connecting your first cloud account, and seeing your savings estimate. Most configurations take under five minutes.

Prerequisites

Before you start, make sure you have:

Provider	What you need
AWS	An AWS IAM user or root credentials for the account you want to connect. Permission to launch a CloudFormation stack.
GCP	A Google account with access to your GCP billing console. Access to Google Cloud Shell.
Azure	An Azure account with permission to create app registrations and assign RBAC roles. Access to Azure Cloud Shell.

You do not need to make any infrastructure changes, install any agents, or modify your workloads.

Step 1: Sign up

1. Go to app.pump.co and create an account.

2. Verify your email address by clicking the link sent to your inbox.

3. Enter your name, job title, company name, company size, and country.

After completing these steps, you land in the Pump dashboard with sample data. The onboarding wizard opens automatically to guide you through connecting your cloud account.

Step 2: Run a savings estimate

The savings estimate is free and requires only read-only access (or a CSV upload). It shows projected savings before you commit to anything.

Click Estimate savings in the onboarding wizard, then select your cloud provider.

AWS

You have two options:

Option A: Grant read-only access (recommended)

1. The wizard generates a CloudFormation Quick-Create Stack URL pre-filled with Pump's read-only IAM role template.

2. Click the link. It opens your AWS Console.

3. Review the stack parameters and click Create stack.

4. The stack deploys a cross-account IAM role with read-only permissions (Cost Explorer, CUR, resource inventory). Pump is automatically notified when the stack completes.

5. Pump generates your savings estimate. This typically takes a few minutes.

Option B: Upload CSVs

1. In your AWS Console, go to Cost Explorer and download two CSV exports: "Costs by Service" and "Costs by Usage Type."

2. Upload both files in the wizard.

3. Pump generates your estimate from the uploaded data.

GCP

1. The wizard prompts you to upload a GCP billing history CSV.

2. Export your billing data from the GCP Console and upload it.

3. Pump generates your savings estimate.

Azure

You have two options:

Option A: Automatic (service principal)

1. Open Azure Cloud Shell and run the command shown in the wizard to create a service principal:

bash

az ad sp create-for-rbac --name pump

1. Paste the resulting JSON (appId, password, tenant) into the wizard.

2. Enter your subscription IDs. The wizard provides a command to list them:

bash

az account list --query"[?state=='Enabled'].id" -o tsv|paste -sd, -

1. Run the Pump-provided script in Cloud Shell to assign the "Billing Reader" role per subscription.

2. Pump verifies access and generates your estimate.

Option B: Upload CSV

1. In the Azure Portal, go to Cost Management + Billing and download your usage file for the last 3 months.

2. Upload the file in the wizard.

3. Pump generates your estimate from the uploaded data.

Step 3: Review your estimate and join Pump

Once your savings estimate is ready, the wizard shows your projected savings. If you want to proceed:

1. Billing partner agreement. Confirm that you agree to have Pump become your billing partner. This means Pump will handle your cloud billing (you receive invoices from Pump instead of directly from your cloud provider).

2. Terms of Service and Privacy Policy. Review and accept.

3. Grant billing permissions. This step varies by provider:

   • AWS: Launch a second CloudFormation stack that deploys an Auto-Pilot IAM role with commitment-purchasing permissions (Reserved Instances, Savings Plans).

   • GCP: Complete a Google OAuth consent flow to authorize Pump's billing access.

   • Azure: Run the Pump-provided Autopilot script in Cloud Shell to assign commitment-purchasing roles (Reservations Contributor, Savings Plan Contributor/Purchaser).

4. Company details. Enter your company profile, including business identification (EIN, GSTIN, or equivalent for your country).

5. Payment method. Add a payment method for Pump invoices.

Your application is submitted. Once approved, Pump begins optimizing your cloud spend.

AWS: Standalone vs Organization

If you are connecting an AWS account, the wizard asks whether your account is part of an AWS Organization.

• Standalone account (not in an AWS Organization): Continue through the self-serve flow described above.

• Part of an AWS Organization: The wizard routes you to schedule a meeting with a Pump solutions architect, since organization-linked accounts require assisted setup.

Step 4: Configure commitment management

After your application is approved, your Pump account team works with you to determine how commitments are managed for your account. This includes how recommendations are reviewed, how purchases are executed, and how renewals are handled.

What happens next

Once connected, Pump begins pulling your historical cost data and optimizing your cloud spend. The depth of historical data varies by provider (see the connection guides for details).

From here, you can:

Action	Where
Invite your team	Navigate to Settings → Team → Invite
Explore your spend data	Open Pump View dashboards
Review security findings	Open Pump Secure
Connect additional cloud accounts	Navigate to Settings → Integrations
Connect third-party services (Anthropic, OpenAI, GitHub, Datadog, etc.)	Navigate to Settings → Integrations