Skip to content
Notifications
Clear all

Banyan pricing feedback - is it too expensive for mid-market?

4 Posts
4 Users
0 Reactions
36 Views
(@diego_h)
Honorable Member
Joined: 6 months ago
Posts: 313
Topic starter   [#22495]

I’m evaluating Banyan Security for a potential Zero Trust implementation. Our team is mid-market, around 300 users, and the per-user pricing feels steep compared to bundling similar features from other vendors.

For those using it, does the cost feel justified by the reduction in admin overhead and security incidents? Or have you found it hard to get budget approval? I’m curious about the real-world ROI, not just the feature list.


Still learning.


   
Quote
(@alexr)
Reputable Member
Joined: 3 months ago
Posts: 356
 

The per-user sticker shock is real, especially at 300 seats where you're paying a premium but missing the volume discounts of larger enterprises. I found the justification hinges entirely on your current admin overhead.

If you're already maintaining a patchwork of VPNs, bastion hosts, and IAM policies, Banyan's operational consolidation can tip the scales. The math we did looked at hours spent per month on access troubleshooting and policy updates, then multiplied by our fully-loaded engineering cost. For us, it penciled out, but just barely.

The harder sell was the reduction in security incidents, which is probabilistic. You're essentially buying an insurance policy with a better control plane. Have you quantified your team's current time spent on access-related fire drills? That's the baseline you need.


Measure twice, cut once.


   
ReplyQuote
(@averyd)
Honorable Member
Joined: 3 months ago
Posts: 477
 

Your point about bundling similar features is key. The "single pane" justification only works if you're actually consolidating multiple point solutions you'd otherwise pay for separately. If you're starting from near zero, the per-user cost is harder to swallow.

We've seen teams treat it as a force multiplier for an existing, overworked SecOps team. The ROI came from reclaiming cycles spent on manual policy updates and access reviews, not just from avoiding hypothetical breaches. Try to map the pricing against those specific, tangible hours - it often looks different than a pure feature-checklist comparison.

The mid-market squeeze is real though. You're paying a premium for an elegant solution without the enterprise bargaining power.


Every dollar counts.


   
ReplyQuote
(@ginar)
Reputable Member
Joined: 2 months ago
Posts: 289
 

The "reclaiming cycles" argument is a classic vendor trap. They love selling you back your own team's time.

But have you actually tracked those manual policy updates to see if they're truly a monthly drain, or just an occasional chore? In my experience, most mid-market teams overestimate the ongoing labor of their cobbled-together systems. The real admin overhead often isn't as high as the sales deck assumes.

You're right about the premium for elegance, but that's the problem. You're paying for polish, not just function, and that's a tough line item to defend when budgets tighten.


Trust but verify.


   
ReplyQuote