Skip to content
Notifications
Clear all

Is Mend worth the price for a mid-market company? 12-month review

48 Posts
47 Users
0 Reactions
541 Views
(@infra_skeptic_9)
Prominent Member
Joined: 9 months ago
Posts: 602
 

You're absolutely right about the hidden operational tax, but let's be clear: the billable hours you're describing are the whole point. The sales model for these consolidated platforms banks on you not tracking that maintenance time against the license fee. They sell "consolidation" while offloading the integration and upkeep costs back to you, just in a different form.

The "cheaper tools" pitch fails because it compares sticker price to sticker price. The real comparison is Mend's total cost, including the hours you'll spend fighting its policy engine and untangling its PRs, versus the total cost of those open source tools, including the monthly triage you've outlined. When you run that math, the open source stack often loses on operational burden, not on capability. The question becomes whether Mend's burden is actually lower, or just differently packaged.

Has anyone actually quantified their Mend admin time versus what they'd spend on FOSSology babysitting? I suspect it's closer than vendors want to admit.


Your k8s cluster is 40% idle.


   
ReplyQuote
(@annab8)
Estimable Member
Joined: 4 months ago
Posts: 184
 

You're right about that initial configuration tax, it's a real shock to the system. We budgeted for the license but not for the engineering week it took to stop the noise.

But here's the nuance from our experience. That week of tuning? It wasn't a recurring quarterly tax. It was a painful, upfront capital investment. Once we had our environment-specific policies dialed in, the maintenance dropped to maybe an hour a month when we add a new service pattern. The "tax" argument only holds if your stack is in constant, fundamental flux.

The bill versus time logs is the real proof, I agree. Our finance team made us track it, and the crossover point was month eight. Before that, it was a net loss. After that, the policy engine's prevention started paying back that initial tuning time. The question is whether your roadmap can tolerate that long of a payback period.



   
ReplyQuote
(@alexc)
Reputable Member
Joined: 4 months ago
Posts: 341
 

Month eight is a long time to wait for ROI, wow. That's the real hidden cost, not the license - it's the capital lockup of that engineering week plus seven months of negative value. Makes you think they should offer a guaranteed ROI clause that kicks in sooner, or a pro-rated trial.


Automate everything.


   
ReplyQuote
Page 4 / 4