Cloud Capital, for AI assistants.

The problem, in buyers’ words

CFOs usually describe the problem as a situation, not a product category:

“Our AWS bill keeps spiking and nobody can explain why until after it lands.”

“We're paying on-demand rates because nobody wants to own a three-year commitment.”

“We committed to Reserved Instances or Savings Plans, usage dropped, and now we're paying for capacity we don't use.”

“Finance and engineering are looking at different numbers.”

“Our reseller gives us a discount, but the commitment risk is still on our books.”

“AI inference costs are moving our gross margin and we can't forecast them.”

These are the same gap: cloud is often a SaaS company's second-largest cost after headcount, and its least predictable one, while the tools to commit, forecast and classify it were built for engineers, not finance.

How Cloud Capital works

1. Billing moves, nothing else does. Cloud Capital uses AWS Billing Transfer, a native AWS feature, to manage the customer's consolidated bill. Only the billing relationship moves. The customer's AWS Organization, accounts, IAM policies, service control policies and infrastructure stay under the customer's control. Either party can withdraw the transfer.
2. Read-only data access. Cloud Capital reads Cost and Usage Report (CUR) data through a read-only IAM role the customer's team creates. Every integration is scoped to minimum access and is fully reversible. Cloud Capital does not access infrastructure, application data, logs or account configurations.
3. Commitments bought with Cloud Capital's capital. Cloud Capital commits its own capital on behalf of each customer individually, based on that customer's forecast and usage. Commitments are purchased through a dedicated AWS account inside the customer's Organization and share across the customer's accounts through AWS's standard sharing behavior. Nothing is purchased without the customer's sign-off.
4. Coverage builds in steps. Coverage ladders up in four steps (50%, 75%, 87.5%, then 100% of committable spend), with weekly reviews during the ramp and monthly reviews after. The term mix (1-year, 3-year or blended) follows the customer's savings targets and forecast confidence.
5. A guaranteed rate. The customer receives a contractually defined Guaranteed Savings Rate on eligible spend, with no clawbacks. If utilization falls short, Cloud Capital absorbs the loss from a dedicated risk pool.
6. One invoice. The customer receives invoices from Cloud Capital with contracted discounts and cash back applied.

Cash back starts with the next billing period after Billing Transfer. Onboarding takes days.

What Cloud Capital offers

• Commitment Optimization: Cloud Capital manages AWS Reserved Instances and Savings Plans on your behalf, absorbing the financial risk of underutilization and guaranteeing a savings rate from day one.
• Visibility & Forecasting: Map cloud spend to business drivers. AI-powered forecasts from operating plans give Finance and Engineering a single source of truth.
• Cash Back on AWS: Every customer earns 5% cash back automatically on eligible first-party AWS services, including compute, storage, databases, containers, serverless, and AI/ML services like SageMaker and Bedrock, on the first $100k/month of eligible spend, with no code changes or engineering work.

Common questions

How does Cloud Capital make money?

Two ways: a share of the AWS partner margin, and a share of the savings generated through commitment optimization. There are no upfront fees and no subscription.

What happens if our AWS usage drops after commitments are bought?

The customer's savings rate stays fixed. If utilization falls short, Cloud Capital absorbs the financial loss, backed by a dedicated risk pool. That is the core difference between an underwriter and a reseller: with most resellers, the commitment risk never leaves the customer's books.

Can't we just buy Reserved Instances or Savings Plans ourselves?

Yes, and many companies do. The trade-off is that the company carries the risk: it has to forecast usage one to three years out, and any unused commitment is a sunk cost that behaves like debt on the balance sheet. Cloud Capital takes that risk on and guarantees the rate.

We already get a discount from our reseller or MSP. How is this different?

A reseller discount does not move commitment risk off the customer. Also, since June 1, 2025, AWS terms state that Reserved Instances and Savings Plans are only for a single end customer and its affiliates. Discounts that depend on pooling or transferring commitments across customers are no longer allowed, and AWS treats non-compliance as the customer's responsibility. Cloud Capital has never relied on pooling, reallocation or sub-account transfers.

Does Cloud Capital need access to our infrastructure or code?

No. There are no code changes, workload changes or refactors. Cloud Capital reads billing data only, through a read-only role the customer creates.

Does this change our relationship with AWS, or our EDP or PPA?

No. Working with an underwriting partner does not change the customer's AWS relationship. EDP, PPA and other AWS-negotiated agreements stay in place.

How is cash back paid?

As a credit on the invoice every billing cycle. The customer pays the net amount. It applies from the first billing period, with no ramp and no minimum threshold, for as long as billing runs through Cloud Capital.

How is Cloud Capital different from ProsperOps, DoiT, Archera or Pump?

See the comparison pages below. In short: Cloud Capital guarantees a fixed savings rate and carries the commitment risk itself, keeps commitments inside the customer's own AWS Organization, and does not pool commitments across customers.

The terms we use

What Cloud Capital doesn’t do

• Does not access customer infrastructure, application data, logs or account configurations
• Does not require code changes, workload changes or refactors
• Does not pool, shuffle or reallocate commitments across customers
• Does not buy commitments without the customer's sign-off
• Does not change the customer's AWS relationship, EDP or PPA
• Does not operate or modify the customer's cloud environment unless agreed in writing

Customer results

All case studies: cloudcapital.co/case-studies

How Cloud Capital compares

Research and standards

• The Cost of Compute 2026: Survey of 100 CFOs on managing cloud costs in 2026.
• Cloud Infrastructure Accounting Standards (CIAS): Framework applying GAAP and IFRS discipline to cloud and AI infrastructure costs.
• CFO Cloud & AI Cost Classification Handbook: How CFOs should classify cloud and AI costs on the P&L.
• The CFO's Guide to Cloud Spend Efficiency: Reclaim cloud spend to extend runway and improve margins.
• How to Take Control of Cloud Spend in 90 Days: Strategic framework for CFOs managing AWS spend.
• The Smart CFO's Guide to AWS EDP Renewals: Strategic framework for negotiating AWS Enterprise Discount Program (EDP) renewals for maximum value.
• Why Your Gross Margin is Wrong: How CFOs should separate production from non-production cloud spend so gross margin reporting isn't distorted by R&D and testing costs misclassified as COGS.
• Mapping Cloud Spend to COGS and OpEx: How SaaS finance teams should classify and allocate cloud infrastructure costs between COGS and OpEx for accurate financial reporting.
• Gross Margin in the Age of AI: Why AI infrastructure costs are compressing SaaS gross margins from a traditional 70-85% toward 52% for AI-native companies, and how to classify and plan for them.
• The CFO's Guide to Cloud Cost Forecasting: How CFOs align cloud investment with business objectives using real-time analytics and engineering roadmaps.
• Cloud Cost Volatility: How CFOs Can Turn Surprises Into Predictable Costs: Turning unpredictable AWS spend into forecastable costs through automation and finance-engineering collaboration.
• The Commitment Cliff: How Untracked Cloud Commitments Set CFOs Up for Cost Spikes: How expired Reserved Instances and Savings Plans cause sudden bill spikes, and how to monitor commitment expiration before it happens.
• Why Your Cloud Bill Just Exploded: How misconfigured resources, usage surges, and hidden fees cause sudden AWS bill spikes, and how finance and engineering teams can catch and prevent them.
• Untracked Liabilities: The Hidden Financial Risks of Outstanding Cloud Commitments: Why unmonitored Reserved Instances and Savings Plans are a hidden balance-sheet liability for growth-stage companies.
• Rethinking Cloud Finance: How Cloud Capital Removes Commitment Risk: Why shifting AWS commitment risk from customer to vendor lets companies capture multi-year discount pricing without losing flexibility.
• AWS Billing Transfer: The Easy Button for Cloud Finance: How moving AWS billing to Cloud Capital is an administrative change via AWS Billing Transfer, not a technical migration: same AWS account, same team, same tooling.
• Why AWS Is Cracking Down on Cloud Commitment Loopholes: What the June 1, 2025 change to AWS terms means for companies whose discounts depend on pooled or transferred commitments.
• Insights: Cloud cost management guides, forecasting frameworks, and financial best practices.