Home / Companies / Logz.io / Blog / Post Details
Content Deep Dive

Elastic is going closed-source. Where does that leave MSSPs?

Blog post from Logz.io

Post Details
Company
Date Published
Author
Eric Thomas
Word Count
970
Company Posts That Month
7
Language
English
Hacker News Points
-
Post removed?
No
Summary

In February 2021, Elastic shifted from an open-source license for Elasticsearch and Kibana to a "source available" license, specifically the Elastic License and the Server Side Public License (SSPL), aiming to restrict competitors like AWS from profiting off their code. This change poses challenges for Managed Security Service Providers (MSSPs), who often use Elasticsearch in their security platforms. While the new licenses prevent the use of Elasticsearch as a service, AWS and Logz.io have responded by announcing an open-source fork of the codebase, potentially offering a community-driven alternative. The new licensing has significant implications for SaaS companies and MSSPs, as it requires releasing their intellectual property if they use ELK stacks in their offerings. Consequently, Logz.io has quickly moved to fork Elasticsearch and Kibana to maintain competitiveness and address the needs of their Cloud SIEM customers, who value interoperability and cost-efficiency.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Observability 2 559 111 33 +17%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.