VMware vRealize (Aria) Licensing Changes
vRealize was rebranded to Aria and absorbed into the VCF and VVF bundles. Standalone Aria is constrained. The licensing position for customers using Aria Operations, Aria Automation, or Aria Logs requires a careful look.
The vRealize product family — vRealize Operations, vRealize Automation, vRealize Log Insight, vRealize Network Insight, and the related management and automation tooling — was rebranded to Aria after the Broadcom acquisition. The new naming places Aria Operations, Aria Automation, Aria Logs, and Aria Networks at the centre of the management stack.
More important than the rebrand, the licensing position has changed substantially. Standalone Aria is constrained. Most Aria functionality is now licensed as a component of VCF or, in restricted form, of VVF. The pre-acquisition vRealize Suite editions have been retired and the standalone purchase paths that existed in the VMware catalogue are no longer the primary commercial route.
The rebrand and product structure
The naming change is straightforward. vRealize Operations became Aria Operations. vRealize Automation became Aria Automation. vRealize Log Insight became Aria Logs (with the SaaS variant also called Aria Operations for Logs in some current materials). vRealize Network Insight became Aria Networks (with the SaaS variant called Aria Operations for Networks). The functionality of each product has continued to develop along its pre-existing roadmap; the rebrand was largely cosmetic.
What changed alongside the rebrand was the catalogue position. The pre-acquisition vRealize Suite editions (Standard, Advanced, Enterprise) were retired. The standalone product purchases were constrained. The functionality was folded into the VCF and VVF bundles as a component.
Aria inside VCF
VCF includes the Aria suite. The exact components included vary by VCF edition and have been adjusted across catalogue revisions, but the general structure as of mid-2026:
VCF Standard
Includes Aria Operations at a limited scope and Aria Logs. Does not include Aria Automation or the more substantive automation tooling. Suitable for customers using basic operations monitoring and log analytics.
VCF Advanced
Includes substantial Aria Operations functionality, Aria Logs at full functionality, and a substantive subset of Aria Automation. Does not include the full advanced automation capabilities. Suitable for most enterprise multi-product VMware estates.
VCF Enterprise
Includes the full Aria suite at the most current functionality. Suitable for customers building substantive self-service private cloud or operating Aria-centred multi-cluster management at scale.
Aria inside VVF
VVF includes a constrained Aria subset. The included Aria components are sufficient for monitoring and basic operations of a vSphere estate but do not extend to the full automation or advanced multi-product capabilities. For customers whose Aria use is principally operational monitoring of a vSphere environment, the VVF Aria subset can be sufficient. For customers running substantial Aria Automation workflows or multi-cluster Aria Operations deployments, VVF's Aria inclusion is too constrained and VCF is the appropriate vehicle.
The VVF Aria subset does not include substantive Aria Automation. Customers running orchestration, blueprints, or self-service catalogues on Aria Automation need at minimum VCF Advanced. Customers using only Aria Operations for monitoring can often work within VVF's Aria subset.
Standalone Aria
Some standalone Aria SKUs persist for specific use cases — particularly the SaaS variants of Aria Operations and Aria Logs, which are sold on a per-host or per-VM basis to customers who want the SaaS deployment model rather than the on-premises version. These remain available but are not the primary commercial direction.
For customers whose VMware deployment is on-premises and whose Aria use is part of the broader management stack, the bundle is the route. For customers running specific point-product needs — for example, log analytics across a mixed-cloud environment — the SaaS standalone variants may be more appropriate.
What Aria customers should do
Three practical actions are appropriate for customers running Aria in the current environment.
First, document current Aria deployment. Which Aria products are in use (Operations, Automation, Logs, Networks), at what scale, with what feature set. This is the foundation for any bundle decision.
Second, map the deployment against the VCF edition matrix. If Aria Automation is in active use with self-service catalogues and complex workflows, VCF Advanced or above is appropriate. If Aria use is principally Operations monitoring, VVF's Aria subset can be sufficient. Match the bundle to the deployment.
Third, evaluate the alternative tooling landscape. The Aria rebrand and bundle absorption has produced a moment when customers are willing to evaluate alternatives to the VMware management stack. Native cloud-vendor tooling (Azure Monitor, AWS CloudWatch, Google Cloud Operations), third-party operations platforms (Datadog, New Relic, Dynatrace), and IT-automation tooling (Ansible, Terraform, ServiceNow) all overlap with parts of the Aria functionality. For customers whose Aria use is not deeply specialised, the alternatives may produce better economics.
Audit considerations
Aria audit risk under Broadcom is largely subsumed into the VCF or VVF audit. Customers running Aria functionality not entitled under their bundle edition produce a finding — for example, Aria Automation in active use under a VCF Standard licence. The product itself enforces some of this but not all, and the audit team checks edition entitlements against deployed functionality.
Aria SaaS variants
The Aria SaaS variants — Aria Operations for Logs, Aria Operations for Networks, and the SaaS-delivered subset of Aria Operations — are licensed independently of the VCF or VVF bundle and represent meaningful commercial paths for customers whose use cases benefit from the SaaS model.
The SaaS variants are typically priced per host, per VM, or per data-ingestion volume depending on the product. The pricing is independent of the underlying VMware infrastructure entitlement, and the SaaS deployment can be used alongside on-premises VMware infrastructure without modification to the infrastructure entitlement.
For customers with mixed-cloud or multi-cloud environments where Aria functionality needs to span beyond a single on-premises VMware estate, the SaaS variants are often the right vehicle. The cloud-vendor-neutral position of the SaaS delivery is also valuable for customers whose strategic direction includes reducing dependency on the on-premises VMware stack.
The Aria Automation question
Aria Automation is the most commercially consequential Aria component in current catalogue revisions. It is the orchestration and self-service catalogue product that enables customers to build substantive private-cloud experiences on top of the underlying VMware infrastructure. The inclusion of Aria Automation is one of the principal differentiators between VVF (where it is absent or restricted) and VCF Advanced (where it is included at substantial functionality).
For customers using Aria Automation in production, the licensing question is settled — VCF Advanced or above is required, and the entitlement is consumed against the core count of the bundle. The deeper question is whether continued use of Aria Automation is the strategic right answer in the post-acquisition catalogue.
Alternative orchestration and automation tooling has matured substantially during the period the Aria rebrand was underway. Terraform with appropriate VMware providers, Ansible with VMware modules, ServiceNow integrated with VMware via the cloud management portfolio, and the cloud-vendor-native automation platforms all overlap with Aria Automation's functionality. For customers building automation strategy from a current-day standpoint, the choice of Aria Automation versus alternatives is open in a way it was not when vRealize Automation was the obvious default.
Aria Operations replacements
For customers re-evaluating Aria Operations, the alternative monitoring and operations platforms are mature and competitive.
Datadog, New Relic, and Dynatrace are the principal commercial alternatives at the operations-platform tier. Each has substantial VMware integration, mature dashboards and analytics, and a SaaS delivery model that compares favourably to Aria Operations for many use cases. The economics depend on host count, data volume, and the specific monitoring use cases — for some patterns the alternatives are cheaper, for others Aria Operations bundled inside VCF is more economic.
Open-source alternatives — Prometheus with Grafana, Zabbix, and various cloud-vendor-native monitoring platforms — are also viable for customers with capable operations teams. The cost differential against bundled Aria Operations can be substantial.
What Aria customers should plan for
The Aria rebrand and bundle absorption is best understood as the first phase of a continued evolution. Customers should plan for the following over the next eighteen-to-thirty-six months.
The Aria functionality inside VCF will continue to develop, with new capabilities added and some legacy functionality consolidated. The current edition matrix is likely to be adjusted in catalogue revisions. The standalone SaaS variants are likely to expand as Broadcom invests in cloud-vendor-neutral positioning for the management stack.
The alternative tooling landscape will continue to mature. Operations, automation, and infrastructure-as-code tooling outside the VMware ecosystem is on an active development trajectory that does not depend on Broadcom's strategic direction. Customers planning multi-year management strategy should explicitly evaluate the alternative direction as a credible path, not as a fallback.
Related reading
For broader context, see the VMware licensing complete guide, VCF licensing explained, vSphere licensing changes, and the end of perpetual licensing.