Elastic Returns to Open Source Roots
In August of 2024, Elastic announced it was adopting GNU Affero General Public License v3 (AGPL 3) as a licensing option for its source code for Elasticsearch and Kibana. This blog summarizes the evolution of Elastic’s licensing from its Apache 2.0 origins, and what this means for users.
A Brief History
Elastic, renowned for its search and analytics platform, has undergone a significant licensing evolution. Initially, they adopted the permissive Apache 2.0 license, which allowed for broad commercial and non-commercial use. This choice fostered rapid adoption and community growth. However, as Elastic’s business matured and concerns arose about the potential misuse of its technology by cloud providers, the company decided to explore more restrictive licensing options.
Introducing SSPL and ELv2
In 2021, Elastic introduced the Server Side Public License (SSPL) and its own Elastic License 2.0 (ELv2). These licenses aimed to address concerns about cloud providers offering managed services based on Elastic’s software without contributing back to the open-source project. The SSPL, in particular, was designed to require any company offering a service based on Elastic’s software to make their source code available under the same license.
Adding AGPL 3 as an Option
Elastic’s latest move is the addition of the GNU Affero General Public License version 3 (AGPL 3) as an additional licensing option for its core products. AGPL 3 is a copyleft license that requires any modified version of the software to be released under the same license, ensuring that any improvements or enhancements made by users are shared back with the community.
AGPL 3 vs. Apache 2.0
Both AGPL 3 and Apache 2.0 are permissive licenses that allow for both commercial and non-commercial use of software. However, there are some key differences between the two licenses:
Copyleft: AGPL 3 is a copyleft license, which means that any software derived from AGPL-licensed code must also be licensed under AGPL 3. Apache 2.0 is not a copyleft license, so derived works can be licensed under any license.
Virality: AGPL 3 is more viral than Apache 2.0. This means that if you distribute a modified version of AGPL-licensed software, you must also distribute the source code for your modifications. Apache 2.0 does not have this requirement.
Server Side Public License Exception: AGPL 3 includes a Server Side Public License Exception (SSPLE). This exception allows you to run AGPL-licensed software on a server and provide access to the software through a network, without having to release the source code for your server-side components.
Impact on Users
The shift to AGPL 3 might have implications for users who intend to modify or extend Elastic’s software for commercial purposes. However, it also reinforces Elastic’s commitment to open source and ensures that the software remains accessible and adaptable for the community.
Conclusion
Elastic’s evolving licensing strategy reflects its ongoing commitment to open source principles and its desire to balance commercial interests with community engagement. By offering multiple licensing options, including AGPL 3, Elastic provides users with greater flexibility and transparency, empowering them to choose the license that best suits their needs and values.
If you have any questions about this license change or need help with your Elasticsearch implementation or migration, please feel free to CONTACT US.
Additional Resources
- Elastic Announces Open Source License for Elasticsearch and Kibana Code | Business Wire
- GNU Affero General Public License – GNU Project – Free Software Foundation
- Apache Licenses (apache.org)
- Elasticsearch Consulting and Implementation Services – Pureinsights
- Elasticsearch vs OpenSearch : Best Explainer Video – Pureinsights