VMware Aria (vRealize) Licensing Under Broadcom
Introduction – From vRealize to Aria
VMware’s vRealize Suite – the well-known toolkit for operations, automation, and cloud management – has been rebranded as VMware Aria. This change isn’t just in name.
Following Broadcom’s acquisition of VMware, the entire licensing model for these products is being reshaped. Broadcom is encouraging customers to move away from traditional perpetual licensing models and toward new subscription or SaaS-based models.
This post examines the changes to vRealize (now Aria) licensing under Broadcom, their implications for enterprises with legacy licenses, and key considerations for negotiating to protect your interests. For a comprehensive overview, read our ultimate guide, ‘VMware Cloud & Advanced Platforms Licensing Under Broadcom: Aria, Cloud Foundation, Tanzu.’
Short answer: Almost everything has changed.
If you’re a customer with substantial vRealize investments, you need to understand Broadcom’s new approach – and be ready to negotiate critical protections in your agreements.
vRealize Licensing Pre-Broadcom
Under VMware’s classic model (pre-Broadcom), vRealize Suite was typically licensed in a perpetual + maintenance model. You purchased a perpetual license for the software and paid for annual support (SnS) to receive updates and ongoing support.
Key points about legacy vRealize licensing included:
- Per-CPU or Per-OSI Metrics: Many vRealize components could be licensed per CPU (processor socket) – especially when part of vRealize Suite or vCloud Suite bundles tied to vSphere. Alternatively, some standalone products (like vRealize Operations when not in a suite) could be licensed per Operating System Instance (OSI) or per VM. This gave customers flexibility to choose a model that fit their environment (e.g., CPU-based licensing for large hosts, or per-VM/OSI for lighter deployments).
- Bundled in vCloud Suite: VMware offered vCloud Suite, which bundled vSphere Enterprise Plus together with vRealize Suite at a discounted bundle price. This meant if you bought vCloud Suite, you essentially got vSphere plus the full range of vRealize management tools (Operations, Automation, Log Insight, etc.) under one license per CPU. Many enterprises leveraged this to deploy vRealize across their estate as part of their infrastructure licensing.
- Perpetual Enterprise Licenses: In large Enterprise License Agreements (ELAs), customers often license vRealize Suite Enterprise-wide. They might have “all you can eat” rights for vRealize across their VMware environment, paying a large upfront sum (CAPEX) and then yearly maintenance. This provided predictability and allowed unlimited usage of vRealize tools within the given scope.
- Standalone vRealize Products: Some organizations also purchased individual vRealize products (like vRealize Operations or vRealize Automation) a la carte. These could be perpetual or subscription, and metrics varied (per CPU, per VM, per named user, etc., depending on the product). However, VMware was flexible – you could buy just what you needed or get the entire suite via bundles.
In summary, before Broadcom, vRealize licensing was fairly flexible, offering options such as perpetual or subscription licensing, CPU-based or VM-based metrics, and availability as a standalone product or as part of bundles like vCloud Suite.
The perpetual model dominated, with customers comfortable owning licenses and renewing support on an annual basis.
Read about Tanzu licensing, VMware Tanzu Licensing Under Broadcom – What Buyers Should Know.
Aria Licensing Under Broadcom
Following Broadcom’s acquisition, VMware’s product portfolio – including vRealize (now Aria) – is being streamlined and shifted toward subscription-based models.
Broadcom has a clear agenda: simplify the offerings, eliminate perpetual licenses, and drive customers to recurring revenue models. Here’s what’s happening with VMware Aria licensing under Broadcom’s regime:
- Rebrand and Simplify: VMware renamed vRealize to VMware Aria, consolidating products such as Aria Operations (formerly vRealize Operations), Aria Automation (vRealize Automation), Aria Operations for Logs (vRealize Log Insight), and others. Broadcom is consolidating these into a simpler SKU structure. Rather than dozens of standalone product SKUs and editions, expect a smaller number of bundled offers. (For instance, Aria “Advanced” or similar bundles that include multiple capabilities in one subscription).
- Subscription-Only Focus: Broadcom is moving VMware to a subscription-only model. As of early 2024, VMware has ceased selling new perpetual licenses for most of its products. All new Aria capabilities are offered via subscription services or term licenses. Perpetual licenses are no longer available for purchase. If you need additional Aria capacity or new features, you’ll be steered to buy a subscription bundle rather than expanding perpetual licenses.
- Credit-Based and SaaS Models: The new Aria licensing is likely to employ a flexible consumption approach. VMware had introduced the concept of Aria Universal credits (formerly vRealize Cloud Universal) where a subscription entitles you to use Aria products either on-premises or as SaaS, drawing down credits. Broadcom will continue with some form of this hybrid SaaS model, but it will wrap it into larger solution bundles (more on that below). Instead of tying licenses strictly to CPUs or OS instances, the subscription might cover access to the whole Aria portfolio (or a subset of it) with usage governed by capacity metrics or cloud credit consumption.
- SKU Consolidation – Aria via Suites: Broadcom has introduced new bundled offerings like VMware Cloud Foundation (VCF) and VMware vSphere Foundation. These are broad subscriptions that include various components:
- VMware Cloud Foundation (VCF): A full-stack subscription that includes vSphere, vSAN, NSX, and the complete VMware Aria suite (all the management and automation tools), plus additional services. This is targeted at enterprises wanting a comprehensive private cloud stack.
- VMware vSphere Foundation (VVF): A slimmed-down bundle for more traditional data center needs. It includes core vSphere features plus some Aria capabilities (notably Aria Operations and Aria Operations for Logs for monitoring, and Tanzu for Kubernetes). It’s meant for mid-sized environments that need more than just basic virtualization.
- No A La Carte Aria: Under Broadcom, you can’t buy Aria products standalone anymore. They’ve reached End-of-Availability as individual SKUs. Suppose you want Aria Operations or Aria Automation. In that case, you can obtain them as part of one of the larger solution subscriptions (such as VCF or vSphere Foundation) or potentially as add-ons to those. This represents a significant shift from the past, when you could simply purchase vRealize Automation on its own. Broadcom’s approach bundles management tools into broader packages instead of selling them separately.
- Perpetual in Maintenance Mode: Existing Aria (vRealize) perpetual products have effectively entered “maintenance mode.” Broadcom will honor support contracts and provide security patches or critical fixes, but no major new features will be delivered to perpetual versions. Innovation will occur primarily in subscription offerings. So the Aria 8.x suite you own now might only get minor updates, while the next-gen capabilities land in Broadcom’s new subscription platforms.
In summary, Aria licensing under Broadcom is primarily based on subscriptions and bundles.
Broadcom simplified VMware’s catalog to encourage customers to purchase larger bundles (often encompassing more than just Aria) as subscriptions.
The flexibility of picking and choosing specific vRealize components or sticking with perpetual licensing is being phased out.
Implications for Perpetual Owners
If you currently own perpetual vRealize (Aria) licenses, you might be wondering: what now? The good news is your licenses remain valid – Broadcom can’t take away the perpetual rights you’ve already purchased.
However, there are serious implications and changes you should plan for:
- Support Cost Hikes: Broadcom is notorious for raising maintenance fees. Don’t be surprised if your annual support (SnS) costs for legacy vRealize/Aria products increase significantly at renewal. They know that perpetual customers are now a captive audience (since new perpetual licenses are no longer sold), and they may use support pricing to encourage a switch to subscriptions. Budget for higher support costs or negotiate caps (more on that later).
- No New Features: As noted, perpetual Aria products are in maintenance mode. New features and improvements will be exclusive to Broadcom’s subscription versions (e.g., new Aria services in VCF or enhancements delivered via SaaS). Perpetual customers might only receive minor patches. This means over time, your software could become stale relative to what’s available to subscription customers. Broadcom may even time-limit how long old versions are fully supported.
- Pressure to Convert: Expect a strong sales push to convert you to Aria subscriptions/SaaS. Broadcom’s playbook likely includes reaching out to all vRealize customers with “conversion offers.” These pitches might warn of end-of-life timelines, highlight the shiny new features you’re missing, or bundle attractive discounts if you migrate now. Be cautious: these initial offers may not be the best deal you can get, and switching to a subscription means recurring costs and potential loss of some perpetual rights (if not negotiated properly).
- Validity of Perpetual Use: Your perpetual license allows you to use the software indefinitely on the versions you own. Broadcom can’t invalidate that. However, they might restrict access to upgrades. For example, if there’s a new version rebranded under Aria 9 or integrated into another suite, they may claim it’s a “new product” not covered by your old SnS. Also, if you need more licenses (to scale your environment), you can’t buy new perpetual ones – you’d have to jump to subscription for the expansion. This effectively limits the growth of your perpetual deployment.
- Risk of Forced Bundles: Another implication is if you do eventually move off perpetual, you might have to buy more than you bargained for. Want to adopt a new feature in Aria Operations? It may only be included as part of a Cloud Foundation bundle that includes numerous other software components (such as NSX). Perpetual customers who were used to buying only what they needed could find the new model forces a broader purchase (and higher cost) than anticipated.
In short, perpetual vRealize owners should be prepared for higher costs and fewer advantages over time.
Broadcom will attempt to make the status quo uncomfortable (or less economical) to encourage you to adopt its new subscription paradigm.
Knowing this, it’s critical to plan your negotiation and strategy whether you stay on perpetual a while longer or consider transitioning to subscription.
Negotiating the Transition
If you decide (or are compelled) to move from perpetual vRealize licenses to Broadcom’s Aria subscription/SaaS model, negotiation is key.
Don’t accept Broadcom’s first quote or standard terms without pushing for concessions to recognize your prior investments and minimize cost shocks. Here are strategic negotiation points for transitioning to Aria subscriptions:
When Converting to an Aria Subscription/SaaS:
- License Credit for Perpetual Investment: Insist on credit for your existing perpetual licenses. You paid good money for those; Broadcom should factor that into the subscription pricing. This can come as a significant discount on the new subscription or an extended initial term. Frame it as a trade-in: you’re effectively trading your perpetual rights for a new subscription, so you should not be paying full price as if you’re a net-new customer. Example clause: “Customer shall receive credit for prior vRealize perpetual licenses when converting to Aria SaaS.”
- Dual-Use Rights During Migration: Migrating from on-premises tools to SaaS or new platforms can take time. Negotiate a “dual-use” period where you can run your legacy vRealize deployment alongside the new Aria subscription. This ensures you can transition without disrupting operations. Aim for at least 12 months of overlap. This way, you can roll out the new solution, migrate content and processes, and decommission the old one in a graceful manner. Example clause: “Customer may run existing vRealize deployments for 12 months alongside new Aria SaaS subscriptions without additional charge.”
- Price Protections (Multi-Year Caps): One risk of subscriptions is the potential for rising renewal costs. Try to lock in multi-year pricing or at least cap the annual increase. For instance, if you sign a 3-year subscription, negotiate that renewals can only increase by a certain small percentage (or even better, fix the renewal price now). This protects you from Broadcom’s well-known habit of hiking prices once you’re dependent on them. A reasonable cap might be 3-5% per year, or a pre-negotiated renewal rate. Example clause: “Subscription renewal pricing shall not increase by more than 5% annually for the first X renewal periods.”
- Retain Upgrade Rights (If Any): If you’re converting some parts of your environment and not others, ensure you maintain support on any remaining perpetual licenses. Also, clarify that any software you continue to run on-prem (if part of a hybrid model) will receive support. Essentially, don’t let the transition inadvertently nullify your support entitlements on products you still use.
If Choosing to Stay Perpetual (For Now):
- Cap Support Fee Increases: As noted, support renewals could skyrocket. Negotiate a cap on support cost increases in writing. For example, agree that your Support and Subscription (SnS) rate for vRealize/Aria perpetual licenses will not rise by more than a certain small percentage each year (or over the contract term). This can often be written into ELAs or support renewal agreements.
- Assure Continued Support Term: Request guarantees that you can renew support for a specified number of years for your current products. Broadcom has ended new sales, but they should still offer support renewals for some time. Get clarity: how long can you keep renewing? If possible, lock in an option to renew support for, say, the next 2-3 years at defined terms.
- Right to Upgrade Within Product Line: If VMware releases minor version updates or patches (e.g., Aria Operations 8.x to 8.y), ensure your support contract entitles you to those, even if major “new” versions are subscription-only. You might not get Aria 9, but you should get any 8.x updates. Clarify this to avoid disputes later.
The overarching strategy is to leverage whatever negotiating power you have now – your existing investment and the fact that Broadcom wants to move you to subscription – to extract better terms.
Once you relinquish your perpetual licenses without conditions, you lose significant leverage. So secure those credits, rights, and caps during the transition negotiation.
Negotiating Within ELAs
Many large enterprises will address VMware Aria licensing as part of a broader Enterprise License Agreement (ELA) or a VMware enterprise agreement that also covers vSphere, vSAN, NSX, and other related products.
Under Broadcom, you need to pay extra attention to how Aria is handled in these big deals:
- Bundle for Better Value: Broadcom’s new approach is to bundle Aria functionality into bigger suites (VCF, vSphere Foundation). When negotiating an ELA, make sure you bundle Aria with core infrastructure products to maximize discounts. For example, if you’re renewing vSphere and NSX, see if you can include Aria Operations/Automation as part of the package rather than a separate line item. A bundled deal could yield a better overall discount percentage and avoid paying the list price for Aria separately.
- Explicitly Cover Aria in the Agreement: Do not assume that Aria tools are automatically included. Spell out in the ELA which Aria components or bundles you are entitled to. If the ELA includes Cloud Foundation, list the components (e.g., Aria suite) that come with it. If it doesn’t include them, be clear on that too. Clarity prevents surprises where you thought you had rights to Aria, but later discover you don’t.
- Protect Against Bundle Uplift: If Aria is included as part of a larger suite (such as Cloud Foundation), be aware of potential hidden cost increases. Broadcom might price Cloud Foundation in a way that effectively charges you for Aria whether you use it or not. Negotiate the total price, but also understand the individual components. If you won’t heavily use Aria Automation, for example, argue for a price that reflects that, or the ability to drop it in a future negotiation. At a minimum, ensure you’re not paying more for overlapping functionality you already own elsewhere.
- Co-term and Cross-Product Considerations: Align Aria’s terms with your vSphere terms. For instance, if you have unlimited vSphere in your ELA, try to obtain an enterprise-wide Aria usage license as well, or at least sufficient licenses to cover your environment. If your ELA allows the deployment of X number of hosts, ensure the Aria part can manage those hosts fully without incurring additional costs. The goal is to avoid a situation where your infrastructure scales under an enterprise deal but your management tools (Aria) hit a licensing ceiling.
- Future-Proof in Writing: Because Broadcom is changing product names and bundles, include language in the ELA that covers successor products. E.g., if you negotiate something for “VMware Aria Suite”, state that it applies to any successor or renamed products providing similar functionality. This protects you if Broadcom rebrands or repackages things mid-agreement.
Negotiating Aria within an ELA is about leverage and clarity. The more you tie it into the overall deal, the better leverage you have (since Broadcom wants the big sale).
Just be sure the contract explicitly grants what you expect, and doesn’t leave Aria as an ambiguous “maybe included, maybe not” area.
Dependencies & Bundling Risks
One major change under Broadcom is how VMware is handling product bundling and dependencies. In the past, VMware’s vCloud Suite bundling was a convenience (you could buy it to get a better price, but it wasn’t mandatory to consume products that way).
Now, Broadcom’s bundling can create risks of over-buying or unwanted components:
- vCloud Suite vs. Cloud Foundation: Historically, vCloud Suite provided vSphere and vRealize Suite together, but you could still choose to purchase them separately. Broadcom’s VMware Cloud Foundation (VCF) is now the flagship bundle: it forces a full-stack (compute, storage, networking, management). If you adopt VCF, you’re getting Aria whether you want it all or not. Similarly, even vSphere Foundation includes some Aria components by default. This bundling means less flexibility to pick only the tools you need.
- No Standalone Purchase: As mentioned earlier, you cannot purchase Aria tools individually at this time. That means if you only need, say, a monitoring solution (formerly vRealize Operations) and nothing else, tough luck – you’ll likely end up buying a bundle that includes lots of extras (Tanzu, NSX, etc.). Customers must clarify whether a particular VMware suite or bundle they’re buying includes Aria and, if so, which specific pieces. If you miss this, you might either end up with a nasty surprise requiring an extra purchase or, conversely, pay for a bundle where half the components (such as Aria Automation or NSX) are essentially useless for you.
- Shelfware and Waste: Unneeded features in bundles can become a waste of resources. For example, a company that only cares about vSphere and basic monitoring might be forced into vSphere Foundation, which also includes Tanzu and Log Analytics that they won’t use. You’re paying for those regardless. This is where negotiation or alternative approaches (like smaller vSphere-only kits) should be considered if available. Always evaluate the cost versus the actual usage of each component in a bundle.
- Cloud Foundation Inclusion: If you’re considering VMware Cloud Foundation (which includes the full Aria suite), note that this is a premium product. Ensure your organization actually needs the whole stack. If you already have other solutions for some components (maybe you use a different automation/orchestration tool), then perhaps pushing for a custom solution or sticking to vSphere Foundation is better than overspending on Cloud Foundation just to get one or two desired features.
- Clarify “Included” vs. “Add-On”: Broadcom has stated that some formerly standalone products are included in VCF or vSphere Foundation by default, while others may be “optional add-ons.” For instance, Aria Operations is included in vSphere Foundation, but what about Aria Automation? It may only be included with the full Cloud Foundation or as an additional cost on top of vSphere Foundation. As a customer, get it in writing which Aria components are included and which are extra, so you’re not surprised by needing an add-on license later.
In short, Broadcom’s bundling can be a double-edged sword. It simplifies procurement (one big package covers your needs), but also risks making you pay for more than you use.
Smart customers will carefully analyze these bundles and negotiate to remove or discount the unused parts, or choose the smallest bundle that meets their requirements to avoid bloat.
Checklist – Aria Licensing Protections
Before signing any deal or renewal with Broadcom for VMware Aria (vRealize) products, ensure you have the following protections and terms in place.
Use this checklist of licensing safeguards to guide your negotiation:
- ✅ Credit for Legacy Licenses: If transitioning to subscription, confirm in writing that you receive financial credit or a discount in recognition of your existing perpetual vRealize licenses.
- ✅ Dual-Use / Transition Period: Secure an agreement that you can run old and new environments in parallel for a defined period (e.g., 6-12 months) during migration to avoid disruption.
- ✅ Price Increase Cap: Include a clause capping annual support or subscription renewal increases (e.g., no more than 3-5% per year). This prevents unwelcome surprises in your IT budget.
- ✅ Bundled Component Clarity: List out which Aria components are included in any bundle you buy. If certain capabilities are add-ons, ensure you know the cost or, if you don’t need them, confirm that you’re not being charged.
- ✅ Support Entitlement Protection: For any perpetual licenses you keep, get assurance that support will continue to be offered for a reasonable term and that you retain rights to patches/updates within that product’s version family.
- ✅ Flexibility for Hybrid Use: If you plan hybrid cloud usage, negotiate any needed bring-your-own-license (BYOL) rights or cloud portability for Aria. (Broadcom is introducing some ability to use subscriptions in the cloud – make sure you can take advantage of that if relevant.)
- ✅ ELA Alignment: In enterprise agreements, align Aria’s terms with the rest of your VMware portfolio. Ensure co-termination dates, coterminous renewals, and consistent discounting across all VMware products to avoid fragmentation.
Having these key items in your contract or quote will significantly reduce your risk and cost over time.
Don’t hesitate to walk away or escalate if Broadcom’s proposals lack these basic protections – they have been more willing to negotiate when customers push back firmly with valid business justifications.
FAQs
Q: Is VMware Aria now subscription-only under Broadcom?
A: Yes. Broadcom has effectively made VMware’s management products subscription-only. VMware Aria (formerly vRealize) is no longer available as a standalone perpetual license for new sales. You can only get Aria capabilities via subscription bundles like VMware Cloud Foundation or vSphere Foundation (or as cloud services if you were on Aria SaaS, which is being phased out). Existing perpetual licenses remain valid, but if you need more or want the new versions, it will be under a subscription model.
Q: What happens to my perpetual vRealize licenses and support?
A: Your existing perpetual licenses remain yours. If you stay on them, you can keep using your deployed vRealize/Aria software indefinitely. Support will continue to be offered, but likely at higher prices and only for the current major version. No new features will be added beyond maintenance updates. Broadcom has announced the end-of-availability for those products, but not the end-of-support yet – typically, you can expect a few years of support life. Keep an eye out for any “end of support” announcements. In the meantime, budget for rising maintenance costs and consider negotiating a support cap or evaluating third-party support providers as an alternative if prices become unreasonable.
Q: Does VMware Aria still bundle with vSphere or VMware Cloud Foundation like before?
A: Under Broadcom, Aria isn’t a separate bundle alongside vSphere – it’s now integrated into the primary bundles. VMware Cloud Foundation includes the full Aria suite as part of that subscription. VMware vSphere Foundation (a new bundle for the data center) includes some Aria components (specifically operations monitoring and log analytics). So yes, Aria comes with these broader offerings by default. However, traditional bundles like the old vCloud Suite (vSphere + vRealize) are essentially replaced by these new subscriptions. If you buy just vSphere Standard (one of the few standalone options left for very basic needs), that will not include Aria. So, clarify your specific product bundle. In short, Aria is bundled, but only in the context of the new Broadcom subscription packages, not as a separate suite you add on to vSphere.
Q: How can I negotiate Aria licensing in a new VMware enterprise deal?
A: Approach it holistically:
- Leverage your existing investments: Ensure the sales team is aware of your significant vRealize deployments – you expect credit for those if you move to the new model.
- Ask for bundle flexibility: If there are components in the bundle you don’t foresee using, bring that to the attention of the seller and push for a better price or an adjusted bundle. They may have some wiggle room via add-on credits or alternative SKUs for specific cases.
- Insist on protective clauses, as outlined in the checklist, including dual–use periods, price caps, etc. These should be included in the contract or, at the very least, the quote’s special terms.
- Get executive alignment: Broadcom’s style is more rigid than VMware’s old approach. It can be helpful to have a high-level conversation (CIO to VMware/Broadcom account executive) stating that your company is concerned about the value and needs these specific terms to remain a customer.
- Consider third-party support or the status quo: As a negotiation tactic, indicate that you’re prepared to maintain your current licenses with third-party support if the subscription offer isn’t compelling enough. Broadcom needs customers to transition to meet its revenue goals, so use that as leverage.
Negotiating with Broadcom will require a firm stance and detailed preparation, but many customers are doing it – you’re not alone in pushing for a fair deal on VMware Aria.
5 Actionable Licensing Tips
To wrap up, here are five actionable tips for enterprises navigating VMware Aria licensing under Broadcom:
- Audit Your Aria Deployment: Start with a clear picture of what vRealize/Aria components you have, what capacity you’re using, and what you actually need going forward. This will help you decide whether you can stick with what you have or if a new solution (and which bundle) is necessary.
- Demand Credit for Past Spend: If you move to a subscription, don’t walk in empty-handed. Explicitly request migration credits or discounts reflecting the money you’ve already spent on perpetual licenses and support. This can significantly reduce the total cost of switching.
- Secure Dual-Use Rights in Writing: Never assume you can just run old and new concurrently – get it in the contract. A 6-12 month dual-use provision is ideal for allowing a smooth transition without double payment.
- Cap Your Renewal Costs: Whether it’s support on existing licenses or a new subscription, negotiate a cap on future price increases. Even a 5% annual increase (compounded) is far better than facing a 20% jump in year two. Lock this in for at least the first 3 to 5 years.
- Integrate Aria into Wider Deals: When signing any VMware ELA or large agreement, make Aria part of the conversation. Even if you’re not ready to use it today, having it included (or at least having the option) at a favorable rate can save you headaches later. Ensure the contract language covers Aria’s inclusion, so you don’t pay extra down the road for capabilities that should have been bundled.
In conclusion, VMware Aria’s licensing has undergone a significant shift under Broadcom’s ownership, transitioning from flexible perpetual models to rigid subscription bundles. Customers need to be strategic and proactive in their approach.
By understanding the changes and negotiating wisely, you can avoid unnecessary costs, preserve your rights, and maybe even turn Broadcom’s push into an opportunity to modernize on your terms rather than theirs.
The key is not to accept the default – leverage your position to achieve the best outcome for your organization’s needs. Good luck!
Read about our Broadcom Licensing Advisory Services
