The Broadcom playbook comes to network monitoring

When Broadcom acquired VMware, infrastructure teams learned a playbook: end perpetual licensing, force multi-year subscriptions, raise renewals by multiples rather than percentages, and accept losing the smaller customers because the remaining ones pay enough to cover it.

Monitoring is now getting the same treatment, and customers have noticed. The most upvoted post on r/Solarwinds in the past year is titled "Solarwinds you're not in the same position as broadcom." The author's argument was simple: the playbook only works when switching is genuinely hard. "Unlike VMware I can change out my network monitoring in under 3 days."

The pattern, three times over

Turn/River Capital acquired SolarWinds and, per customer reports across dozens of threads, moved quickly: perpetual licensing retired globally, three-year subscription terms as the default, renewal quotes arriving 40% to over 300% above prior spend, negotiable down but rarely to parity.

Here is the detail most affected customers discovered only mid-escape: Turn/River also holds a strategic investment in Paessler, the maker of PRTG. PRTG went through the same transition earlier, and PRTG users in the threads describe it in identical terms: perpetual scrapped, roughly 2.5x price increases, mandatory three-year contracts. Multiple SolarWinds customers announced they were fleeing to PRTG, only to be told by PRTG customers that they were running toward the same owner and the same playbook, a few years further along.

One customer described the strategy from the inside of a renewal negotiation: "They only want the whales who are willing to pay the extra over starting from scratch. Real shame. Customer retention with a gun to their head." Another thread cited an expectation, attributed to company communications, of losing at least 20% of customers by design.

Whether every detail is accurate, the observed behavior is consistent, and it matches the economics. A private equity owner optimizes for revenue per customer and predictable subscription income within a defined hold period. Long-tail customer goodwill is not on that spreadsheet.

Why loyalty stopped mattering

The threads are full of tenure: 13 years, 17 years, 18 years, 20 years, "customer since 2006ish." Every one of them got the same quote structure as a new logo, sometimes worse, because long-tenured customers were sitting on the oldest, cheapest agreements with the most room to "correct."

This is the uncomfortable lesson for buyers. Under this ownership model, your loyalty is not an asset you hold. It is an asset the vendor holds, priced as switching cost. The only counterweight you control is making that switching cost visibly low: exportable inventories, documented alert logic, config archives in open formats, and a tested alternative. Customers who arrived at renewal with a competing quote report materially better outcomes than customers who arrived with tenure.

Ownership is now an evaluation criterion

Infrastructure teams evaluate vendors on features, support, and price. The last two years argue for a fourth criterion: who owns the vendor, and what is that owner's track record at renewal time?

Practical questions worth asking any monitoring vendor, in writing, before you commit:

Who owns you, and has that owner changed licensing models at other portfolio companies? What happens to my deployment if I do not renew? What contractual limits exist on renewal increases within and after my term? And if ownership changes during my term, what protections carry over?

A vendor that will not answer these plainly has answered them.

None of this means avoiding every PE-owned product; some are run well. It means pricing the risk consciously instead of discovering it in a renewal quote, and weighting founder-owned or otherwise stable vendors accordingly when the products are comparable.

Where Sensaka fits

Sensaka is a founder-owned European company building a unified infrastructure operations platform: monitoring, hardware-layer visibility, asset and configuration management for data center teams. We put terms and renewal treatment in writing before you commit, because we think the last two years have made that a baseline requirement, not a differentiator.

If you are re-evaluating your monitoring stack in light of all this, we are happy to be the competing quote in your renewal meeting, and to earn the longer conversation from there.

Further reading: explore SolarWinds Alternatives, Multi-Vendor Hardware Monitoring, Sensaka DCOS, and Redfish & IPMI Reference.