Skip to content
Notifications
Clear all

Am I the only one who finds the license calculation overly complex?

3 Posts
3 Users
0 Reactions
57 Views
(@henryg)
Honorable Member
Joined: 4 months ago
Posts: 420
Topic starter   [#26318]

Trying to get a real quote for Cybereason feels like a logic puzzle. It's not endpoints + users. It's endpoints, plus users, plus servers, plus some multiplier based on the phase of the moon and whether you're using their cloud or your own.

You end up needing a spreadsheet just to model the licensing for a proof of concept. Compare that to a straightforward per-endpoint model. This complexity isn't a feature; it's a tax on your time and a great way to obscure the true three-year TCO. Makes you wonder what exactly you're locking yourself into.


Your vendor is not your friend.


   
Quote
(@emmal)
Reputable Member
Joined: 4 months ago
Posts: 320
 

Yeah, the spreadsheet comment hits home. I've seen this in other platforms too. That complexity often pushes the sales conversation toward "let us build a custom quote for you," which just removes any chance for you to model it independently.

It does make you wonder if the obscurity is intentional, to make price-shopping between vendors harder. You end up comparing one unclear quote to another.

Have you gotten to the point where they actually provided a detailed breakdown, or does it stay as a single, vague number?



   
ReplyQuote
(@averyc)
Reputable Member
Joined: 4 months ago
Posts: 225
 

You're right that the custom quote removes independent modeling. The times I've gotten a detailed breakdown, it came as a spreadsheet from them with dozens of tabs and hidden columns. It's technically a "breakdown", but you can't extract a clear unit cost for anything. It's just as opaque as the single number.

The intentional obscurity for vendor lock-in comparisons is the real cost. You can't get a clean apples-to-apples on a per-seat or per-core basis because they've invented new fruit. This isn't just a sales tactic; it's an architectural decision to make migration financially incalculable later.

My rule now is if I can't model the licensing cost in a simple script with our own inventory data, we walk away. The operational complexity always mirrors the licensing complexity.


Show me the benchmarks.


   
ReplyQuote