Number of Seats/Users: CloudHealth Automation offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows CloudHealth Automation that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from CloudHealth Automation. CloudHealth Automation reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: CloudHealth Automation offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from CloudHealth Automation. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: CloudHealth Automation often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that CloudHealth Automation is seen as a strong cost and governance layer on top of cloud environments, especially for VM-heavy workloads.

From what Spendbase clients tell us, the main strengths look like this:

• Cost optimization & savings
• Clear visibility into cloud spend across instances
• Easy identification of idle or over-provisioned resources
• Good reporting for infrastructure costs (when set up correctly)
• Health & performance monitoring
• Lightweight agents are quick to deploy and easy to automate
• Central portal to track VM health, disk space, disk usage, and basic security incidents
• Good fit for multi-client or multi-account setups
• Automation & scalability
• Works well with automation accounts and scheduled deployments
• Once configured, can scale across many VMs without heavy manual effort
• Governance & control
• Policy-driven approach aligns with business processes
• Helps balance faster innovation with governance and cost control

At the same time, our internal data also highlights some recurring pain points:

• Reporting complexity
• Custom reporting is described as “finicky”
• It’s easy to accidentally impact global reports when trying to build narrower, account-specific views
• This can become a blocker for finance and FinOps teams that need precise segmentation
• Limited PaaS coverage
• Strong focus on VMs and IaaS, but weaker coverage for:
  • Web Apps
  • Service Bus
  • Traffic Managers
  • Other PaaS services
• Spendbase clients managing modern, PaaS-heavy stacks often feel they need additional tools or manual workarounds
• Feature depth beyond core use cases
• Excellent for VM health and cost, but expectations are rising around:
  • Deeper security insights
  • Broader resource coverage
  • More intuitive analytics and dashboards

From a Spendbase discount perspective, this means CloudHealth is usually a great fit for:

• Organizations with a large VM footprint who want cost optimization and governance
• Teams already using automation to roll out agents at scale

But we recommend negotiating more aggressively or checking for complementary tools if:

• Your environment is heavily PaaS-based
• Your team needs very granular, self-service custom reporting without risk of breaking global setups