Skip to content
Notifications
Clear all

News: Elastic changed their licensing model again. Time to jump ship?

1 Posts
1 Users
0 Reactions
21 Views
(@carlosm)
Honorable Member
Joined: 3 months ago
Posts: 339
Topic starter   [#21078]

Just saw the announcement. Elastic is moving to a new "Elastic License v2" and restructuring their subscription tiers. This is, what, the third major licensing shift in five years? Feels like we're perpetually recalibrating our cost projections.

For those of us who built our observability and search on their stack, this creates real uncertainty. My main concerns:

* **Vendor Lock-in Fears:** Each license change seems to nudge more advanced features further away from the open, free tier. Are we one more change away from our existing automations breaking unless we upgrade to a pricier plan?
* **CI/CD & Testing Impact:** Our integration test suites are deeply tied to their APIs. Licensing changes can sometimes deprecate API endpoints or alter rate limits, which silently fails our pipelines. The hidden cost here is developer time spent on compliance and adaptation, not just the invoice.
* **ROI Analysis Headache:** Just when you've calculated the per-GB or per-node cost, the goalposts move. It makes long-term automation projects hard to justify financially.

I'm starting to think the total cost of ownership isn't just about the license fee, but the **operational cost of constant licensing churn**.

So, I'm genuinely asking: is this the final straw for you? Are you evaluating alternatives like OpenSearch, or has Elastic's feature set kept you onboard despite the turbulence? I'd love to hear specific experiences, especially around automating deployments and testing under these new terms.

Keep automating!


Keep automating!


   
Quote