Broadcom vs. VMware Users: What This Means for the Future of Software Ownership

Broadcom’s latest move, sending cease-and-desist letters to VMware users (and customers) with perpetual licenses, isn’t just a licensing update, it’s a warning. As reported from multiple sources, including Wired, customers who bought VMware are now being told to either start paying a subscription or stop using it altogether.

As reported by Ars Technica, which posted an alleged copy of the cease and desist letter, this appears to not only be a theoretical threat—but instead– a legal one which includes enhanced reporting requirement obligations and potential fees and penalties owed. This type of action demonstrates just how fast ownership, and usage rights, can vanish in today’s software landscape.

After Broadcom acquired VMware in 2023, they seem to have taken steps to decrease support teams, terminate the perpetual licensing model, and push customers toward subscription-only plans. Now, it’s taken it a step further: it threatens potential legal action against anyone still using previously purchased perpetual versions of VMware products. This is a stark reminder that when support becomes tied to strict licensing enforcement, flexibility and long-term continuity can take a back seat.

At HeroDevs, we don’t just see this as Broadcom making changes to its licensing policies. Instead, we view this as a broader signal for teams relying on legacy software, Spring included, to carefully select their vendors. Users and enterprise customers alike must ensure vendors (and the software they provide) not only meet the technical requirements to achieve success, but also have a clear track record and ever-present alignment with customer values, which are tightly aligned–in our opinion–to open source. 

‍

If It Can Happen to VMware, It Can Happen to Spring

VMware Tanzu Spring is part of the broader Broadcom portfolio, and while no similar action has been reported yet, it’s worth watching closely. As Spring Framework 5.x and other versions approach or reach end-of-life, users may find themselves navigating new terms or limited options—especially if official support shifts toward a more rigid or subscription-only model.

At HeroDevs, we offer support for end-of-life software, including Spring Framework—and we do so transparently, without locking customers into timelines or forcing migrations. Our goal is to provide freedom and stability, not to limit it, and we achieve this through our Never-Ending Support offerings and operating in a way which embraces open source values. 

For those relying on Spring, and want to stay ahead of potential changes, now’s the time to think proactively about your options.

‍

How HeroDevs Approaches Support

HeroDevs was founded on the belief that critical open-source software shouldn’t become a liability just because official support ends. Our Never-Ending Support (NES) model gives teams a reliable path forward—secure, compliant, and built around real-world timelines.

As open-source software continues to evolve and play a critical role in every environment, HeroDevs has partnered with the world’s largest open source communities like the OpenJS Foundation, Drupal Association, Linux Foundation and many others. 

HeroDevs takes pride in not only providing the most secure and reliable end-of-life open source software–but also–partnering with, and directly supporting, the open source communities and individuals that build these tools. 

‍

What This Means for Teams Using Spring or Other EOL Frameworks

This situation highlights how quickly software terms can shift under new ownership. If you're using Spring, especially versions nearing or past end-of-life, now is the time to review your support strategy.

‍

Final Word

Software support should offer continuity, not pressure. At HeroDevs, our role is to extend the life of the tools you depend on, without surprise pivots or lock-in tactics.

Your systems. Your timeline. Your call.

‍