Comment on Elasticsearch is open source, again
limonfiesta@lemmy.world 2 months agoThis company may be dogshit, but seat count is the standard licensing structure for most employee facing business software, including on-prem.
And most business licensing requires that information to generate a quote, as price will be dependent upon several factors, including volume licensing tiers.
Sometimes, licensing structures are simple enough that an employee or rep might be able to give you a quick ballpark without that information, but that would be the exception, not the rule.
tiny@midwest.social 2 months ago
Usually in the observability space it is primarily based on the volume of data and sometimes seat count. Especially if it’s freemium like elastic where users can get an idea of volume by running a POC of the free version
limonfiesta@lemmy.world 2 months ago
Generally that elastic or usage/volumetric based billing structures are used on SaaS/cloud products, not on-prem.
Although it’s entirely possible that elasticsearch, and other vendors in the space use that building model for their on-prem customers.
Regardless, that’s even more of a reason why it would be very difficult to give a quote without being first having a presales meeting with a solution architect or knowledgeable rep.
maniii@lemmy.world 2 months ago
How about instead of elastic customers moved to Redis or Postgres ?
Does the pricing/licensing suddenly change ? Hmm ?
xthexder@l.sw0.com 2 months ago
Elasticsearch provides a different feature set than Redis or Postgres. I’ve seen apps that use all 3… but anyway.
It is a little weird to charge per-seat for a search database that is usually integrated into a product, and not used directly by employees. Usually that kind of pricing model is reserved for developer tools like Splunk (notoriously overpriced), or game engines like Unity/Unreal Engine.