We’ve got exciting news from the open-source world: Elasticsearch and Kibana are once again being called Open Source. This move is sure to bring joy to tech enthusiasts and developers who hold open-source values close to their hearts. Let’s delve into what this means and why it’s such a significant development.

AGPL Licensing: A New Chapter

Elastic has announced that they will be adding AGPL as another license option alongside ELv2 and SSPL. This may sound like just another licensing change, but it’s quite a big deal. By adopting AGPL, an OSI-approved license, Elastic can now officially call Elasticsearch and Kibana Open Source again. This move eliminates any lingering doubts or misconceptions about their open-source status.

The Journey Back to Open Source

Three years ago, Elastic made the tough decision to change their license due to issues with AWS and the confusion their offering was causing in the market. This decision led to a fork and brought about a different trajectory for Elasticsearch. However, Elastic always maintained their commitment to open-source principles despite the licensing change.

Success Through Strategic Changes

Fast forward three years, and it seems that the strategy has worked. Amazon has fully invested in their fork of Elasticsearch, much of the market confusion has been resolved, and Elastic’s partnership with AWS is stronger than ever—they were even named AWS Partner of the Year. With these positive changes, the time is now right for Elastic to return to being a fully open-source project.

More Choices for Users

Adding AGPL as a license option is all about providing flexibility. Users who prefer ELv2 (a BSD-inspired license) or SSPL will see no change. For those who favor AGPL, another open-source license, this option is now available. If you’re currently using Elasticsearch and happy with your setup, you can continue without any disruptions.

Why AGPL?

Choosing AGPL is a calculated move. Elastic aims to pave the way for more options in the open-source licensing world. Projects like Grafana, which also moved from Apache2 to AGPL, show that this license doesn’t hinder adoption or popularity. Elastic’s collaboration with OSI could potentially lead to even more open-source options in the future.

A Welcome Return to Open Source

The return of Elasticsearch and Kibana to the open-source fold is a momentous event. It underscores Elastic’s long-standing commitment to open-source values and their adaptive strategies to navigate market challenges.

Clearing Up Common Questions

Such significant changes often lead to questions and concerns. Here are a few anticipated ones and their clarifications:

• “Was changing the license a mistake?” Changing the license three years ago addressed significant market confusion. The landscape has evolved, and Elastic’s proactive steps then have enabled today’s positive change.
• “Is AGPL really open-source?” AGPL is an OSI-approved license and widely accepted in the open-source community. It doesn’t impact the usage or popularity negatively, as evidenced by its adoption by projects like MongoDB and Grafana.
• “Is Elastic changing the license because they’re struggling?” On the contrary, Elastic is thriving. Recent launches like Stateless Elasticsearch and ES|QL, and advancements in their SIEM product in Security, demonstrate their ongoing innovation and growth. This licensing change aligns with their long-term vision.

Overall, this shift marks a positive step for both Elastic and the broader open-source community. Welcome back, Elasticsearch and Kibana, to the world of Open Source!