VMware Aria Suite (vRealize / VCF Operations and Automation)¶

Scope¶

This document covers the suite-level view of what was historically the vRealize suite, rebranded to the Aria suite in 2022-2023, and renamed again to VCF-prefixed products (VCF Operations, VCF Automation, VCF Operations for Logs, VCF Automation Config) in VCF 9.0 under Broadcom. It addresses the questions a buyer or architect asks at the suite level rather than at the individual product level: which components exist and what they were called across the rebrands, on-prem self-managed vs SaaS deployment models, sizing across the suite as a system, post-Broadcom licensing and bundling (where the suite components sit inside VCF vs separately purchased), suite-level operations and integration, and suite-vs-point-tools alternatives. For depth on individual products see providers/vmware/observability.md (VCF Operations / VCF Operations for Logs) and providers/vmware/platform-services.md (VCF Automation and Automation Config).

Checklist¶

Components and naming history¶

[Critical] Which generation of the suite is actually deployed, and is naming consistent across documentation, runbooks, and operational artifacts? (vRealize 8.x vs Aria 8.12+ vs VCF 9.0; the same product has had three names in three years and stale runbooks referencing "vRealize Operations" or even "Aria Operations" when the environment is on VCF 9.x cause confusion and incorrect KB lookups against the Broadcom support portal)
[Critical] Is the inventory of which components are actually in use documented, distinct from what is licensed? (VCF Operations, VCF Automation, VCF Operations for Logs, VCF Operations for Networks (formerly Aria Operations for Networks / vRealize Network Insight), VCF Automation Config (formerly SaltStack Config / Aria Automation Config), VCF Automation Orchestrator (formerly vRealize Orchestrator), Aria Hub / Aria Graph, Aria Cost (with CloudHealth absorption); many environments license the bundle but actively use only Operations and Logs)
[Recommended] Has discontinued or absorbed branding been mapped to its successor? (vRealize Business for Cloud was discontinued and partially absorbed into Aria Cost / CloudHealth; Aria Hub and Aria Graph were Broadcom-era unification layers whose roadmap status should be confirmed with the current Broadcom account team before designing around them)

Deployment model¶

[Critical] Is the suite deployed on-prem self-managed, as a SaaS-hosted control plane, or hybrid (SaaS control plane with on-prem collectors)? (On-prem gives full control of upgrade cadence and air-gap compatibility but the customer owns appliance backups, certificate rotation, and version compatibility; SaaS shifts that operational burden to Broadcom but requires outbound connectivity and creates a vendor dependency for availability of the control plane)
[Recommended] For on-prem deployments, is the appliance high-availability topology defined? (VCF Operations analytics cluster with multiple data nodes plus a witness for HA; VCF Automation HA with at least three nodes; VCF Operations for Logs cluster with multiple nodes plus an integrated load balancer; single-node deployments are POC-only and a production outage if treated as production)
[Recommended] Is air-gapped or restricted-egress operation a requirement, and which suite functions degrade without internet access? (On-prem appliances run fully air-gapped but content packs, management packs, and KB-matching for proactive support require either internet access or a periodic offline content-pack download workflow; SaaS deployment is not viable in fully air-gapped environments)

Sizing¶

[Critical] Is VCF Operations sized to the count of monitored objects rather than the host count alone? (Sizing is driven by total managed objects -- VMs, datastores, network ports, container objects, plus management packs -- not just ESXi hosts; the official sizing tool buckets deployments into extra-small / small / medium / large / extra-large with steep node-count and memory deltas at each tier, and undersizing produces silent metric loss rather than a visible failure)
[Recommended] Is VCF Operations for Logs sized to the actual ingestion rate (GB/day) and retention requirement, not just the host count? (A noisy NSX firewall log source or a misconfigured application logger can dominate ingest; cluster nodes vs forwarder topology decisions depend on per-source rate and where retention is anchored)
[Recommended] Is VCF Automation sized for both steady-state catalog/blueprint load and the day-2 operations queue? (Steady-state provisioning rate, concurrent approvals, and the long-running ABX/extensibility actions; under-sizing manifests as queued requests and timeouts rather than outright failure, which is easy to miss in early operation)

Licensing and bundling¶

[Critical] Is it understood that under Broadcom there is effectively no standalone "Aria Suite" SKU for new purchases, with the suite components consumed primarily through VCF (full stack) and to a more limited extent through VVF (vSphere Foundation)? (VCF includes VCF Operations, VCF Automation, VCF Operations for Logs, and VCF Automation Config as part of the bundle; VVF does not include them; the historical vRealize Suite Standard / Advanced / Enterprise editions and the later Aria Universal Suite subscription are legacy SKUs being phased out at renewal -- verify current entitlements with a Broadcom-authorized partner rather than assuming continuity)
[Recommended] Has the per-core licensing impact of consuming the suite via VCF been calculated against the suite's actual usage? (Because VCF licensing is per-core on ESXi hosts and includes the suite, the marginal cost of using more of the suite is zero -- but if only VCF Operations is used, the bundled VCF Automation and VCF Automation Config represent unrealized value; conversely, dropping to VVF to escape unused bundling forgoes the suite entirely)
[Recommended] For organizations holding legacy perpetual vRealize / Aria licenses, has the support-renewal trajectory been mapped? (Broadcom does not renew support on legacy perpetual licenses indefinitely; once support lapses, no patches and no Broadcom-authorized assistance, and the migration path is to a VCF or VVF subscription; this is a renewal-pressure timeline that drives suite-vs-alternative decisions)

Operations and integration¶

[Recommended] Are appliance backups configured for every suite appliance, with restore tested? (Some Aria/VCF Operations versions do not support in-place upgrade-failure rollback -- the documented recovery is restore-from-backup; vCenter-level VM snapshots are not a substitute for the application-aware backup procedure on Operations and Automation appliances)
[Recommended] Is the upgrade path across the rebrand boundaries planned -- vRealize 8.x to Aria 8.12+ to VCF 9.0 -- with the order of operations matched to the SDDC Manager dependency? (Inside VCF, SDDC Manager orchestrates suite upgrades alongside vCenter, NSX, and ESXi; outside VCF, the customer owns the dependency matrix and the cross-rebrand upgrade path can require stepping through intermediate versions)
[Recommended] Are integrations with vCenter, NSX, and SDDC Manager configured correctly so the suite is the single pane of glass it is marketed as? (Adapter / endpoint credentials with least-privilege service accounts; management packs for non-VMware infrastructure to extend coverage; SDDC Manager integration for VCF lifecycle visibility; without these integrations the suite degrades to a partial view that fails to justify its cost)
[Optional] Is multi-tenancy required, and which product provides it? (VCF Automation supports projects/business groups and quotas, and tenant apps have historically been used in service-provider deployments of vRealize Operations; multi-tenancy adds significant configuration complexity and is often misapplied to environments that only need RBAC)

Alternatives¶

[Critical] Has the suite been evaluated against point-tool alternatives at the suite level, not component-by-component? (VCF Operations vs Prometheus + Grafana + Loki for VMware observability; VCF Automation vs Terraform + Ansible + a thin self-service portal for IaaS; VCF Operations for Logs vs Splunk or Elastic; VCF Automation Config vs upstream Salt or Ansible -- the suite's value is in integration across these, so an alternative built from point tools needs explicit integration design or it will be operationally worse than the suite even when each individual tool is better)
[Recommended] Has the suite been compared to a competing cloud management platform (CMP) rather than only to point tools? (Morpheus -- now HPE-owned -- and ServiceNow Cloud Provisioning and Governance are direct alternatives to VCF Automation at the self-service IaaS layer, and Morpheus in particular is positioned as a VMware-exit-friendly CMP under Broadcom renewal pressure; see providers/morpheus/cloud-management.md for depth)

Why This Matters¶

The Aria suite -- whatever it is called this quarter -- is one of the largest VMware spend lines after the hypervisor itself, and it is also one of the most affected by the Broadcom acquisition. Pricing, packaging, and even the product names changed within an 18-month window: vRealize Suite (Standard / Advanced / Enterprise) gave way to the Aria Universal Suite subscription in 2022-2023, and the Aria branding was itself superseded in VCF 9.0 by VCF-prefixed names. Architects walking into a VMware engagement frequently find runbooks and ADRs that reference all three generations of naming, which makes KB searches against the Broadcom support portal fail and which obscures whether a given recommendation still applies to the installed version.

The bundling change is the larger commercial issue. Under Broadcom, the suite is primarily consumed through VCF, which means a customer who only wants infrastructure monitoring is now buying a per-core subscription that also includes automation, log analytics, and configuration management -- whether those are deployed or not. Conversely, customers on VVF do not get the suite at all, and adding it after the fact is not always possible at a price that beats moving to VCF. This is a fundamentally different shape than the old a-la-carte vRealize line.

The renewal-pressure dynamic is what makes a unified suite file necessary rather than just component-level files. The decision to renew under Broadcom's terms vs to migrate the suite's workload off VMware is rarely about a single product -- it is about whether the integrated value of Operations + Automation + Logs + Config justifies the bundle price, and whether a replacement stack of point tools (or a competing CMP) can deliver comparable integration at lower TCO including migration cost. That decision deserves an explicit ADR, not a series of disconnected component-level decisions.

Finally, the deployment-model question (on-prem vs SaaS vs hybrid) has changed character under Broadcom. SaaS-hosted suite services that were once part of the Aria Cloud story have been consolidated and rebranded; what is actually available as SaaS today should be confirmed with a Broadcom-authorized partner rather than assumed from older documentation, because the public-facing pages have churned.

Common Decisions (ADR Triggers)¶

VCF Operations vs Prometheus + Grafana + Loki -- VCF Operations for deep VMware-native semantics, capacity and right-sizing analytics, and pre-built dashboards aligned to vSphere/vSAN/NSX object models vs Prometheus + Grafana + Loki (with vSphere exporters and the OpenTelemetry collector) for a cloud-native observability stack that extends across VMware and non-VMware workloads at lower licensing cost but with significant build-and-maintain effort
VCF Automation vs Terraform + custom IaaS portal -- VCF Automation for GUI-driven self-service catalogs, approval workflows, lease management, and day-2 operations as a packaged product vs Terraform (with the VMware provider) plus Ansible plus a thin web portal (Backstage, custom React, ServiceNow) for an IaC-first stack that integrates better with developer pipelines but requires the organization to own the portal and approval engine
Suite vs point tools -- The full VCF-bundled suite for integrated cross-product workflows (a VCF Automation provisioning event flows into VCF Operations capacity tracking and VCF Operations for Logs audit records without custom glue) vs an assembled stack of best-of-breed point tools that requires explicit integration design; the suite's value proposition is the integration, not any individual product being best-in-class
On-prem self-managed vs Aria Cloud SaaS -- On-prem for full control over upgrade cadence, air-gap compatibility, and data residency, at the cost of owning appliance backups, HA topology, and version compatibility vs SaaS-hosted control plane for reduced operational burden at the cost of outbound connectivity requirements, vendor dependency on the control-plane availability, and a SaaS roadmap that has churned under Broadcom
Stay on the suite under Broadcom renewal vs migrate to alternative -- Renew the suite under VCF or VVF terms to preserve existing operational expertise and avoid migration risk vs migrate observability to Prometheus/Grafana/Loki or Datadog, migrate automation to Terraform plus a portal, and migrate logs to Splunk or Elastic, with the decision driven by renewal-cycle pricing, the integration value actually being realized, and the team's appetite for operating a non-vendor stack
Buy the full Suite (via VCF) vs use only VCF Operations -- Adopt the full bundled suite to maximize value extracted from VCF licensing (since the components are already paid for in the per-core subscription) vs deliberately use only VCF Operations and treat the bundled VCF Automation and VCF Automation Config as shelfware, on the basis that operating only what is actually needed reduces appliance count, upgrade burden, and integration complexity
Aria Cost / CloudHealth vs native hyperscaler cost tooling vs third-party FinOps -- Aria Cost / CloudHealth for multi-cloud cost visibility with VMware-private-cloud awareness vs native AWS Cost Explorer / Azure Cost Management / GCP Billing for first-party depth on each hyperscaler vs Vantage / Cloudability / Apptio for vendor-neutral FinOps; under Broadcom the CloudHealth roadmap and inclusion in VCF have moved, so verify current entitlement before designing around it

Reference Links¶

VMware Cloud Foundation on Broadcom -- current VCF product page including which suite components are bundled
Broadcom TechDocs portal -- post-acquisition consolidated documentation home; the former docs.vmware.com URLs for vRealize and Aria products now redirect here
VMware end-of-life lifecycle matrix -- vRealize and Aria product end-of-support dates relevant to renewal planning