SolarWinds is ending perpetual licenses. The real change is what happens when you stop paying.

In mid-2025, resellers began telling SolarWinds customers that perpetual licensing was going away globally, replaced by subscription. Customers on r/Solarwinds confirmed it within weeks. The pricing implications got most of the attention. The structural change deserves more.

Two very different failure modes

Under a perpetual license, not renewing maintenance meant losing support and updates. The software kept running. Customers in the threads confirmed this directly: asked whether self-hosted perpetual licenses keep working without an active maintenance contract, the answer was yes. One PRTG customer, having been through the same transition with that product, described keeping their perpetual install running unsupported on an air-gapped network as a deliberate fallback position.

Under the subscription model, not renewing means the platform stops. One customer summarized the Hybrid Cloud Observability terms plainly: lapse your billing and polling stops. Your monitoring, your alerting, your historical baseline, off.

That is the change that should drive your planning. Perpetual licensing gave you a slow, controlled degradation path: run unsupported for a year while you migrate, patch nothing, accept the risk consciously. Subscription gives you a cliff. Every future renewal negotiation happens with your observability held as collateral.

What this does to your leverage

Vendors understand this asymmetry, which is why the subscription conversion is paired with three-year terms. Once your monitoring turns off at non-renewal, and once you are committed for three years at a time, your negotiating position at each renewal is structurally worse than it was under perpetual maintenance. Several customers described exactly this dynamic: "By forcing me into a subscription, you're basically encouraging me to cancel," wrote one, noting that under perpetual they simply ran without support and bought help when needed.

There is also a conversion trap reported in the threads. Customers who moved from perpetual to subscription describe attractive transition pricing in year one, with contractual escalation in years two and three. If you are evaluating a conversion offer, the number that matters is the last year of the term, not the first.

The questions to answer before you convert

If you hold perpetual SolarWinds licenses today, you hold an asset. Before trading it for a subscription, get written answers to four questions.

What exactly stops working at non-renewal under the new terms, and after what grace period? Do not accept a verbal summary of this.

What are the year-two and year-three prices in the term, in numbers, not discount percentages off an unstated list?

Can you retain your perpetual entitlements in parallel, even unsupported? Some customers negotiated conversions without surrendering existing keys. An unsupported perpetual install is an ugly fallback, but it is a fallback.

And what is the data-export path? Node inventories, historical performance data, alert definitions, config archives. If the platform stops at non-renewal, your exit tooling has to exist before you need it. Community-built export scripts already exist for node and SNMP target extraction; know where they are.

The larger pattern

SolarWinds is not doing anything unusual. Perpetual licensing is disappearing across the monitoring market because subscription revenue values a software company more highly. PRTG made the same move under the same ownership. Others will follow. The practical conclusion for infrastructure teams is not "find a vendor that promises perpetual forever." It is: treat licensing terms as an architectural dependency, the same way you treat a single-vendor hardware lock-in, and design your monitoring estate so that no single commercial decision by a vendor can turn your visibility off faster than you can replace it.

That means keeping inventories exportable, alert logic documented outside the tool, config backups in an open format, and at least one evaluated alternative on file. Portability is not disloyalty. It is the only thing that keeps renewal conversations honest.

Where Sensaka fits

Sensaka is a unified infrastructure operations platform covering network, server, and hardware-layer monitoring with asset and configuration management built in. We are direct about terms before you commit, and we will put pricing for your actual environment in writing, including what happens at the end of a term, so you can compare structures and not just headline numbers.

If you are weighing a perpetual-to-subscription conversion, talk to us first. Worst case, you walk into that negotiation with a real alternative in hand.

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