ProsperOps returns cloud spend to your budget

By design, our service operates automatically in the background, executing thousands of real-time optimizations that respond to evolving usage patterns, architectural changes, and business demands. However, the platform is governed by customer-defined controls to ensure transparency, flexibility, and alignment with organizational policies.

Many teams benefit from ProsperOps, including Finance, Engineering, Product, and Operations. ProsperOps sits at the intersection of DevOps and FinOps, where fragmented management of commitment-based discounts (such as RIs, SPs, and CUDs) often leads to misalignment. ProsperOps helps bridge that gap through automated, data-driven optimization that aligns cost efficiency with operational agility.

The ProsperOps pricing model is different than most SaaS products and is directly tied to cloud savings generated (versus cloud spend):

• Organic usage growth notwithstanding, your cloud budget will benefit from a lower cloud bill.
• In addition, the savings generated from the cloud bill more than offset the ProsperOps fee.
• With a term commitment, ProsperOps offers tiered pricing that delivers scalable economics as your savings increase.

The ProsperOps charge is called the Savings Share and is a function of savings calculated in dollars, driven by the rates applied against Inherited Savings, Base Savings, Flex Savings and Smart Savings.

• For AWS
  • Inherited Savings are the monthly savings generated from all customer-procured Reserved Instances and Compute Savings Plans.
  • Base Savings are the monthly savings generated from batch-purchased Compute Savings Plans that ProsperOps has purchased.
  • Smart Savings are the monthly savings generated from Reserved Instances and/or Adaptive-Laddered Compute Savings Plans that ProsperOps has purchased or optimized as part of the Services.
• For Google Cloud
  • Inherited Savings are the monthly savings generated from all customer-procured compute discount instruments (e.g., Committed Use Discounts (CUDs) and Compute Flexible CUDs).
  • Base Savings are the monthly savings generated from a Spend-based Compute Flexible CUD that ProsperOps has purchased as part of the Services.
  • Smart Savings are the monthly savings generated from a Resource-based CUD that ProsperOps has purchased or optimized as part of the Services.
• For Microsoft Azure
  • Inherited Savings are the monthly savings generated from all customer-procured Reservations and Compute Savings Plans.
  • Base Savings are the monthly savings generated from Azure Compute Savings Plans.
  • Smart Savings are the monthly savings generated from Reservations that ProsperOps has purchased or optimized as part of the Services.

ProsperOps only needs least-privilege access to actively manage your commitment discount portfolio and passively monitor your billing data across your multi-cloud estate. No agent is required, only an IAM role or Service Principal (Azure). For our Commitment Management offering, that role prevents us from manipulating (i.e., launching, starting, stopping, terminating) your engineering resources, and we cannot access your AWS, Azure, or Google Cloud resources or services. As such, ProsperOps cannot impact application performance, availability, etc. But, for ProsperOps Scheduler, we require additional permissions to start and stop resources as part of its automation.

We’re firm believers in the security principle of least privilege, so our permission set includes only the minimum access required to optimize your cloud costs.

Learn more about the specific permission levels required for each of our services:

For AWS:

• Limited IAM Permissions for an AWS Savings Analysis
• Limited IAM Permissions for AWS Compute Active Discount Management
• IAM Permissions for Enabling ProsperOps Scheduler

For Azure:

• Limited IAM Permissions for an Azure Savings Analysis
• Limited IAM Permissions for AWS Compute Active Discount Management

For Google Cloud:

• Limited IAM Permissions for a Google Cloud Savings Analysis
• Limited IAM Permissions for Google Cloud Compute Engine Autonomous Discount Management

While we hope to save you money for the long term, you can cancel your subscription at any time.

If you cancel the subscription, you will be billed the Saving Share charge for the current month-to-date. Since the Savings Share includes savings over the contract term of managed commitment-based discounts, you will also be billed a final Savings Share charge for future-to-be-realized savings of all ProsperOps managed commitments on AWS, Azure, and Google Cloud. See our service terms for additional details.

Subscriptions are monthly by default. If you are interested in a longer term plan, please contact our team.

Yes. For any prepayment our service deploys beyond monthly spend, customers must first approve a quarterly budget that acts as an additional constraint for our service (when applicable, this shows up as an additional setting in our Console). In that model, we produce a projected quarterly budget just before the beginning of each quarter, which you review, adjust if you want, and approve. Once approved, our algorithms will only deploy prepayment in that quarter if it’s within the approved budget.

Upon a customer’s termination, ProsperOps will immediately bill the savings share charge for Services provided month-to-date.

Suppose a customer terminates a ProsperOps-managed discount instrument before its term expires. In that case, the unrealized savings share charges are due for the remaining reserved instance term, up to a maximum of 12 months.

Estimated unrealized fees vary across agreements. If you have specific questions around unique scenarios related to unrealized savings share fees, schedule a demo to speak with our team.

No, in Early Access, customers can use ProsperOps Scheduler to automate resource state changes on weekly schedules to reduce waste and decrease cloud spend.

While having an in-house FinOps team is helpful, manual handling of commitments becomes more complex as scale and complexity increase. FinOps teams must analyze workload patterns, predict usage trends, align purchases and renewals, coordinate across Engineering and Finance, and balance flexibility with savings—all while navigating different discount instruments, terms, and rules across multiple cloud providers.

ProsperOps automates this entire process and executes in near real-time, transforming it from a manual, error-prone effort into a precise, proactive system that ensures consistent savings and allows FinOps teams to focus on higher-value initiatives that need human expertise.

Building an in-house FinOps tool may seem viable, but it comes with significant engineering, financial, and operational complexity. ProsperOps automates this entire process by continuously adapting to cloud changes, optimizing for cyclical workloads, and delivering higher savings than most self-built systems can sustain. Even after accounting for our fee, customers consistently achieve better financial outcomes without the burden of maintaining complex internal infrastructure. In short, ProsperOps lets your team focus on strategic initiatives while we handle the precision and scale of automatic cost management.