VMware Aria (formerly vRealize) is Broadcom's enterprise management and observability platform for cloud infrastructure and applications. Under VCF, Aria components are bundled in ways that create both operational value and significant cost traps. This guide explains Aria Suite tiers, what VCF includes, standalone Aria pricing models, the Aria Automation cost factor, and how to avoid overpaying for management capabilities you don't use.
VMware Aria is the rebranded suite of management and observability products formerly known as vRealize. The rebranding reflects a broader evolution: from vRealize as a set of standalone management modules to Aria as an integrated platform for infrastructure observability, cost governance, automation, and application performance across hybrid cloud and on-premises environments. Under Broadcom's ownership, Aria components have been reorganised, some have been consolidated, and new packaging options have been introduced that significantly affect pricing.
The core Aria components address three strategic use cases: (1) Observability — understanding the health, performance, and resource consumption of infrastructure and applications; (2) Automation — defining and executing lifecycle management workflows across hybrid cloud; and (3) Cost Governance — tracking, allocating, and optimising cloud spending across AWS, Azure, GCP, and on-premises. The bundling of these capabilities into VCF has created a tension: organisations that only need one or two of these capabilities must evaluate whether the VCF bundle price justifies the additional Aria components they don't intend to use.
VMware Aria consists of six major components, each addressing a specific operational need. Understanding what each component does is critical to understanding whether the Aria components included in VCF represent value or waste for your environment:
| Aria Component | Old Name (vRealize) | Primary Use Case | Included in VCF | Standalone Subscription | Pricing Basis |
|---|---|---|---|---|---|
| Aria Operations | vRealize Operations | Infrastructure performance, capacity planning, health monitoring | Yes (Standard) | Yes | Per VM or per instance |
| Aria Operations for Logs | vRealize Log Insight | Centralised log aggregation, analysis, and troubleshooting | Yes (limited) | Yes | Per GB ingested/day |
| Aria Operations for Networks | vRealize Network Insight | Network flow visibility, micro-segmentation planning, troubleshooting | Limited | Yes | Per VM or per flow |
| Aria Automation | vRealize Automation | Infrastructure provisioning, IaC, lifecycle orchestration, self-service | No | Yes | Per VM or per deployment |
| Aria for Logs (advanced) | vRealize Log Insight (premium) | AI/ML-driven log analysis, anomaly detection, security analytics | No | Yes | Per GB ingested/day |
| Aria Cost | CloudHealth (in transition) | Multi-cloud cost analytics, allocation, governance, FinOps tooling | No (sunsetting) | In transition | Per resource/month |
VMware's transition from vRealize to Aria nomenclature can be confusing in renewal documentation. Verify whether you are being quoted for "Aria Operations" (the new name, included in VCF) or legacy "vRealize Operations" product names. Old vRealize licences may not automatically convert to Aria equivalents at renewal, and negotiating the transition terms is a material cost lever.
VMware Cloud Foundation subscriptions include specific Aria capabilities as part of the per-core bundle. Understanding exactly what is included in VCF versus what must be purchased separately is critical to identifying cost traps and negotiation opportunities.
| Aria Component | VCF Included? | Limitations / Edition | Must Purchase Separately? |
|---|---|---|---|
| Aria Operations | Yes | Standard edition, up to licensed core count | Advanced/Premium if needed |
| Aria Operations for Logs | Yes | Basic tier, limited retention and query capability | Advanced/Enterprise for premium features |
| Aria Operations for Networks | Limited | Read-only access, NSX flow visibility only | Full platform license required for management |
| Aria Automation | No | Not included in VCF at any tier | Always purchased separately |
| Aria for Logs (premium) | No | Premium/ML capabilities not in VCF | Separate Aria for Logs Advanced subscription |
| Aria Cost | No | CloudHealth transitioning to cloud-only model | Separate subscription, no perpetual option |
The critical finding: VCF includes Aria Operations (Standard) and Aria Operations for Logs (Basic). This provides foundational infrastructure observability and log aggregation. However, VCF does not include Aria Automation — the provisioning and orchestration component — and includes only limited Aria Operations for Networks capabilities. Organisations that assumed "VCF includes all Aria" frequently discover at renewal that they have separate Aria Automation subscriptions they did not realise were outside VCF scope.
For organisations purchasing Aria components outside of VCF, Broadcom offers several packaging options that affect pricing and cost negotiation:
Aria Suite Standard: Includes Aria Operations (Standard) and Aria Operations for Logs (Basic). Available as a standalone subscription per VM. Pricing is typically £180–220 per VM annually, depending on core count and term commitment. This is relevant for organisations running non-VMware infrastructure who need Aria observability without the VCF bundle.
Aria Suite Advanced: Includes Aria Operations (Advanced), Aria Operations for Logs (Advanced), Aria Automation, and Aria Operations for Networks (full platform). This is the tier that includes the full Aria platform stack. Standalone Advanced pricing is significantly higher than VCF — typically £550–750 per VM annually for the full stack. This premium over VCF reflects the fact that many organisations deploying VCF have already paid for these capabilities in the bundle, so the standalone pricing must be premium to maintain pricing discipline.
Aria Suite Enterprise: Adds Aria Hub (cross-cloud management), advanced cloud connectors, and enterprise support. Enterprise tier pricing exceeds £1,000 per VM annually in some markets. Most organisations do not need this tier unless managing 1000+ VMs across 5+ public cloud providers.
Aria Component Licenses: Individual components can be licensed separately — Aria Operations alone, Aria Automation alone, Aria Cost alone. This allows organisations to purchase only what they need, but per-component pricing is generally less favourable than suite pricing because it removes the bundling discount. Use component licensing only when one specific capability is required independent of others.
VCF customers frequently assume that all Aria capabilities are included in the per-core VCF price. They are not. Aria Automation — the infrastructure provisioning and IaC component — is never included in VCF and must always be purchased separately. At renewal, verify whether you have active Aria Automation subscriptions that were previously negotiated as part of a broader Aria or VMware deal. Many organisations are surprised to find Aria Automation subscriptions in their renewal proposals that were bundled in old VMware contracts and have been carried forward.
The distinction between Aria Operations and Aria Operations for Networks creates frequent licensing confusion and cost trap opportunities:
Aria Operations provides infrastructure performance monitoring, capacity planning, and health analytics for vSphere VMs, physical servers, and cloud instances. It collects performance telemetry from hypervisors, agents, and cloud APIs to provide dashboards on CPU utilisation, memory pressure, storage latency, and resource contention. Standard edition (included in VCF) provides foundational dashboards and alerting; Advanced and Premium tiers add features such as predictive capacity analytics, cost allocation, and advanced security monitoring.
Aria Operations for Networks (formerly vRealize Network Insight) provides network flow visibility — understanding which VMs communicate with each other, external systems, and cloud services — and supports micro-segmentation planning by identifying actual network traffic patterns. For organisations planning NSX micro-segmentation deployments, Aria Operations for Networks is the logical tool to understand your current network dependencies.
The licensing distinction matters: Aria Operations for Networks is priced separately and has different scope counting than Aria Operations. Organisations that assume "Aria Operations includes network visibility" are often surprised at renewal when Aria Operations for Networks is presented as a separate line item. Additionally, VCF includes read-only Aria Operations for Networks (for NSX flow visibility), but the full platform for network analysis must be purchased separately.
Aria Automation is consistently the most expensive Aria component and the source of the largest negotiation opportunities. Unlike Aria Operations (which is largely passive observability), Aria Automation actively provisions, configures, and manages infrastructure based on policies and automation workflows. This is strategically important but operationally complex and frequently over-scoped.
What Aria Automation does: It enables self-service infrastructure provisioning (allowing application teams to request VMs, networks, and storage without manual IT intervention), infrastructure-as-code (IaC) workflows, VM lifecycle management (rightsizing, decommissioning, chargeback), and cross-cloud orchestration. For organisations with mature DevOps practices and cloud-native architectures, Aria Automation is highly valuable. For organisations still primarily managing infrastructure manually or through simple vSphere automation, Aria Automation is often oversold and underutilised.
Aria Automation pricing: Standalone Aria Automation subscriptions are priced per VM deployed (or per VM managed, depending on licensing model). Typical pricing is £400–550 per VM annually for organisations with large deployment bases. For a 500-VM environment, this translates to £200,000–275,000 per year for Aria Automation alone. Because Aria Automation is not included in VCF, every organisation must make an explicit decision about whether to license it — and at what scope.
Aria Automation negotiation opportunities: The most common cost reduction tactic is scoping reduction — licensing Aria Automation only for VMs that are actively managed by Aria Automation workflows, rather than licensing all VMs in the vSphere inventory. In many organisations, only 40–60% of VMs are actually deployed and managed through Aria Automation. The remainder are deployed and managed manually or through other orchestration tools. Auditing which VMs are genuinely managed by Aria Automation and excluding the remainder from the license scope can reduce Aria Automation cost by 30–50%.
Aria Operations for Logs (basic, included in VCF) provides centralised log aggregation but with limitations on retention period, query capability, and analysis features. Organisations that require advanced features — such as ML-driven anomaly detection, longer retention periods (beyond 30 days), or integration with security and compliance workflows — must purchase Aria for Logs Advanced as a separate subscription.
Aria for Logs pricing model: Unlike VM-based pricing for Aria Operations, Aria for Logs is priced per GB of logs ingested per day. A typical organisation with 100 VMs and comprehensive logging (system, application, network security logs) ingests 50–150 GB of logs daily. At £0.05–0.08 per GB per month, this translates to £3,000–14,000 per year for Aria for Logs — not massive in absolute terms but easy to miscontrol if ingestion patterns are not monitored.
Log ingestion controls: One of the most frequently overlooked cost management levers is reducing unnecessary log ingestion. Organisations that send all VM system logs, application logs, and security logs to Aria for Logs can easily over-ingest. Defining retention tiers (high-value security logs retained for 90 days, general system logs for 14 days, debug logs not ingested at all) can reduce per-GB costs by 40–60%. This requires no negotiation with Broadcom — it is pure operational discipline.
Aria Cost (formerly CloudHealth): Aria Cost is VMware's multi-cloud cost analysis and governance tool. It was acquired through the CloudHealth acquisition and is transitioning to a cloud-only subscription model. There is no Aria Cost perpetual licence — all Aria Cost usage is subscription-based. For organisations with complex multi-cloud cost allocation requirements (AWS + Azure + on-premises), Aria Cost is valuable. For organisations with primarily on-premises infrastructure, the cost-benefit is marginal. Aria Cost is frequently bundled into broader Aria or VMware deals; at renewal, verify whether you actually use Aria Cost dashboards and whether open-source alternatives (Kubecost for Kubernetes cost visibility, CloudZero, Harness for general cloud cost analysis) might be more cost-effective.
Uncertain About Your Aria Automation Scope?
Our advisors provide Aria Automation scope audits, VCF + Aria bundled renewals, and Aria cost optimisation for enterprise deployments.