SolarWinds Customers Are Furious: The Subscription Shift Feels Less Like Progress and More Like a Shakedown

# SolarWinds Customers Are Furious: The Subscription Shift Feels Less Like Progress and More Like a Shakedown ## The bill didn’t just go up. It changed the relationship. There’s a special kind of panic that hits when a vendor stops sounding like a partner and starts sounding like a toll booth. That’s the mood around SolarWinds right now, after customers began hearing that perpetual licensing is being pushed aside globally in favor of subscription pricing. For teams looking at products like NPM, NCM, and UDT, the question wasn’t some abstract “future of software” debate. It was simpler and colder: is this actually happening, and are we about to get cornered before the end of August? The answer from people dealing with renewals was blunt. Yes, it appears to be true. And for many, the price isn’t creeping upward. It’s jumping like someone cut the brake lines. The frustration isn’t just about subscriptions. Plenty of IT teams already live in that world. The anger comes from the feeling that a tool they built process, staffing, dashboards, alerts, and budgets around is suddenly being repriced around someone else’s spreadsheet. One person summed up the dread by comparing the move to the Broadcom playbook: higher pricing, reduced flexibility, and customers left scrambling to justify a bill that no longer looks anything like last year’s. Another said their renewal went from $9,500 on perpetual licensing to more than $30,000 on subscription, even after a 43 percent “longtime customer” discount and a three-year commitment. That kind of discount doesn’t feel generous when the invoice still punches you in the mouth. ## Customers are comparing notes, and the notes are ugly The most striking thing about the reaction is how specific the stories are. This isn’t vague vendor grumbling. It’s procurement scar tissue. One customer said their renewal increase for perpetual licenses was near 10 percent, while others reported jumps of 100 percent, 200 percent, even 500 percent when bundles were added that they didn’t want. A Database Performance Analyzer customer said a three-year renewal arrived with a 25 percent first-year discount, then smaller discounts after that, while the actual increases over the old renewal price rose by 200 percent, 236 percent, and 276 percent. After 17 years as a customer, their reaction was basically: probably not anymore. That’s the danger with these transitions. The vendor sees migration. The customer sees betrayal with line items. Some people are taking the hard-nosed route: negotiate like leaving is already on the table. One commenter said the magic words were “Never pay MSRP.” Their team moved from perpetual within the same budget they had for a normal renewal. Another self-hosted customer said they told the reseller they’d walk to Paessler or ManageEngine, showed old maintenance pricing, asked for a multi-year commitment, and ended up with pricing close to their previous annual cost plus 5 percent. A nonprofit healthcare team said their manager simply drew a budget line and refused to cross it: this is what we have, no wiggle room. SolarWinds made it work. That’s the uncomfortable lesson hiding in the noise: the first quote may be a test, not a verdict. ## The HCO pitch works for some, but not everyone is buying it Hybrid Cloud Observability is becoming the escape hatch SolarWinds would like customers to choose, but the community is split on whether it’s a sensible landing zone or just a new cage with nicer paint. One person said they were subscribing to HCO for three years and would know later whether the move paid off. Another said HCO can make financial sense, but only under the right conditions. If you’re a larger enterprise and need SQL Sentry, NCM, SAM, NTA, IPAM, and other modules, the bundle may work out better than buying pieces separately. That’s the optimistic version: more capability, cleaner licensing, maybe a better long-term platform if your environment is big enough to use it. Then there’s the other version. For teams that only need two modules, HCO may not be cheaper at all. The billing model changes the math. You may not pay for additional polling engines in the same way, but you do pay for every non-ICMP node, and if your billing lapses, Orion stops polling. ICMP-only nodes may be free, but once you attach another module, such as a SAM template, that node becomes billable. That’s not a tiny footnote. It’s the kind of detail that can turn a migration quote into a budget trap. If the old world was messy but predictable, the new one feels cleaner only after you count every edge case. And IT teams live in edge cases. ## The alternatives look tempting until the work shows up When pricing spikes, everyone suddenly becomes open-minded. WhatsUp Gold, LogicMonitor, PRTG, ManageEngine, Entuity, Dynatrace, InvGate, and Zabbix all came up as possible alternatives. ManageEngine got some praise as a cheaper option that still offers perpetual licensing, with one person saying they had shifted and were satisfied. WhatsUp Gold was mentioned as supporting SNMPv3 and AES-256, which mattered to a customer who couldn’t easily find a replacement that met their encryption needs. Zabbix drew the strongest emotional pull because it offers the dream every angry renewal meeting creates: monitor what you want without paying the vendor forever. One person said they were leaving by year-end, keeping SolarWinds servers up without support during the transition, and moving to Zabbix. But the more cautious voices pushed back hard on the fantasy that migration is just a software swap. Zabbix can handle basic up/down checks, compute monitoring, interface metrics, and custom SNMP polling. That doesn’t mean it magically recreates years of SolarWinds dashboards, alert logic, reports, dependencies, and executive-friendly views. You may need Grafana. You may need outside consulting. You’ll almost certainly need time. One person considering Zabbix still argued that even paying for consultation and support could be worth it if the total cost lands at half the SolarWinds support figure. That’s the real trade. You can pay the subscription tax, or you can pay with labor, risk, and a few very long nights. PRTG also triggered warnings because some users saw a familiar movie playing there too. One person said PRTG went through the same playbook: perpetual licensing scrapped, subscription pushed, prices multiplied. Another PRTG user said their move to subscription-only brought 2.5x increases and mandatory three-year contracts. Their advice was almost survivalist: don’t accept the first offer, don’t panic, keep the perpetual license if you can, say no to transition discounts, and wait for a win-back team to come around with deeper discounts. They claimed discounts of 60 percent or more can appear later if you have the nerve and the runway. That’s not normal vendor management. That’s hostage negotiation with a purchase order. ## The subscription economy has a trust problem There is a pro-subscription argument, and it shouldn’t be dismissed just because the invoices are making people swear at their monitors. Software vendors need recurring revenue to fund product development, support, security fixes, cloud services, and predictable roadmaps. Perpetual licensing can leave vendors supporting old versions for years while customers delay upgrades and revenue gets lumpy. One commenter even said they were happy about the subscription shift and that SolarWinds should have done it years ago. From that angle, the problem isn’t the move to subscription. It’s the size of the increases, the bundling pressure, and the sense that customers are being shoved instead of guided. That distinction matters. IT teams can handle change when it feels earned. They can sell a cleaner platform to leadership if the value is obvious. They can accept annual increases when the product is improving, support is responsive, and the migration path feels sane. What they can’t easily accept is a repackaged bill that removes choice, demands multi-year lock-in, and adds modules nobody asked for. One customer described sitting through a marketing demo for bundled services they had no interest in, stopping the conversation after 15 minutes because the sales team wasn’t listening. A few weeks later, sales kept pestering them anyway. That’s how a pricing change becomes a brand problem. The ugliest part is that many customers still seem to like the product enough to hesitate before leaving. That’s why this story has heat. People don’t get this mad about tools they never cared about. SolarWinds is embedded in environments where ripping it out means risk, time, politics, retraining, and probably some broken dashboards along the way. That gives the vendor leverage, but leverage is not loyalty. Push too hard, and customers start building exit plans even if they can’t leave tomorrow. They freeze upgrades. They run pilots. They call competitors. They let unsupported servers limp along while they rebuild monitoring from scratch. That’s not churn on a slide deck. That’s trust walking out the back door. The practical takeaway is brutal but clear: don’t treat the first renewal quote as reality. Inventory every node. Know which modules are actually used. Separate must-have features from nice-to-have bundles. Bring old maintenance pricing, competitive quotes, and a migration timeline to the table. Ask for multi-year price protection if you stay. And if you’re looking elsewhere, don’t compare license costs alone. Compare the full blast radius: dashboards, alert tuning, SNMPv3, AES-256, reporting, support, training, integrations, and the human cost of rebuilding what already works. The subscription shift may be the future. But for a lot of SolarWinds customers, it doesn’t feel like the future arrived. It feels like the invoice did.