Ten years of Orion: what a product that stopped moving costs you

In a thread about renewal price increases, a long-time SolarWinds customer offered a hot take: "There has been no innovation in Orion or SAM in the last 4 years. The only thing they've been doing is patching vulnerabilities."

The first reply: "4 years? Try 10."

The response to that: "I was trying to be very generous."

Strip the bitterness and there is a serious question underneath: what does it actually cost an operations team to run on a product that has stopped moving? The SolarWinds threads, read together, give an unusually concrete answer, because the same users document both the stagnation and the workarounds it forces.

The stagnation, in the users' own words

The specifics customers cite are small individually and damning in aggregate. The platform still runs on .NET 4.8, a framework generation behind, noted with disbelief by a customer wondering whether the development organization is "mired in internal politics." The web interface has shipped as a jarring mix of old and new page designs for roughly a decade, two UI generations coexisting without convergence. Orion maps still cannot draw curved lines colored by bandwidth utilization, a visualization request old enough to vote. A thirteen-year veteran and community MVP weighs recommending against his own specialty. And the acquisitions that did happen puzzled the customer base more than they excited it; "what's the point of a monitoring company acquiring Serv-U?" stands in for a decade of portfolio drift.

Meanwhile the company's current headline investment, an AI agent, landed with its own community flatly unimpressed: the annual flagship event built around it ran under an hour of substance by attendee accounts, and the reaction ranged from "pretty big letdown" to security-history skepticism about giving it access at all.

Stagnation is not neutral. It compounds.

A static product does not simply fail to delight. It exports work to its users, and the threads document exactly where.

The mobile gap is the cleanest example. Checking alerts from a phone was painful enough that a community member built and now sells his own third-party mobile app, at $9.99 a month, to do what the platform would not. The community's response was gratitude, which tells you how long the gap stood.

Alert delivery is another. When Verizon retired its email-to-SMS gateway, teams relying on it for paging were left to assemble their own answers from third-party SMS services and incident platforms, comparing notes in the forum, because the product offered no native path. Alert hygiene generally has the same texture: one admin could not modify an alert definition without triggering over a thousand duplicate emails, and the accepted answer was a manual disable-change-wait-enable dance.

Each gap breeds a workaround; each workaround becomes unowned infrastructure: scripts, third-party subscriptions, tribal sequences that live in one admin's head. That is the real invoice for stagnation, and it arrives monthly, in hours.

Paying more for the same is the breaking point

Teams tolerated all of this at the old prices, which is why the current moment is different. The renewal quotes arriving now, 40% to several hundred percent above prior spend, are attached to the same static product; customer after customer makes the point that the increase comes with "zero added value to justify" it. Rising price against a flat capability line is the specific combination that converts tolerant veterans into migrators. The 18-year and 20-year departures in these threads are not rage-quits. They are the arithmetic finally clearing.

There is an evaluation lesson here that outlasts any one vendor: judge a platform by its shipping velocity, not its feature list. Ask what has actually shipped in the last twelve months, look at the release notes as a body of work, and check whether community feature requests from five years ago are still open. A vendor's recent past is the most honest forecast of your next three years with them.

Where Sensaka fits

Sensaka is early in its life in Europe, which has a specific advantage: the platform is being built now, on current foundations, with a roadmap shaped by exactly the gaps this article describes, hardware-level depth, honest alerting, asset truth, and operational workflows that do not require a sideloaded ecosystem of workarounds. We are happy to be judged by the standard above. Ask us what shipped in the last twelve months, and we will show you the changelog.

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