Note translator. X-Pack is a proprietary extension for ELK products.

From open communications to free software, openness has always been in the spirit of Elastic.
Therefore, we open the proprietary code X-Pack. X-Pack includes functionality related to security, alerts, monitoring, as well as reports, analytics and machine learning.

Why do we do this?

Initially, we created X-Pack as a set of proprietary functionality that extends the Elastic stack - Elasticsearch, Kibana, Beats and Logstash. Some features, such as monitoring, were free. Some, for example, security and machine learning were paid.

Our company is built on a combination of open source and commercial benefits (for more details, see Shay ). Opening X-Pack code should speed development and increase community involvement. Everyone can contribute, comment and learn the code.

What will change on Github?

The code from the X-Pack private repositories will be moved to the corresponding public repositories Elasticsearch, Kibana, Beats and Logstash. We do not change the Apache 2.0 license for the Elasticsearch, Kibana, Beats, and Logstash code. And never will be. We create in each repository a new X-Pack directory, which will be distributed under the Elastic EULA license. This license allows you to contribute some more derivative actions.

Thus we get rid of problems with the constant synchronization of different github repositories. We also speed up build, testing and releases. In addition, we now have one place where everyone can create and track issues.

How will this affect usability?

Starting from version 6.3, all free X-Pack functionality (monitoring, Search Profiler, Grok Debugger, APM UIs, etc.) will be delivered in standard assemblies Elasticsearch, Kibana, Beats and Logstash.

We remove all restrictions - registration by email, separate installation, full restart of the cluster. This simplifies the quick start of development, allows you to use additional functionality out of the box. As a result, allows us to more effectively use our technology.

In case you prefer to use only open source under the Apache 2.0 license, we will provide the '-oss' versions of the builds.

OSSFL: Open Source Software for Life

We believe in open source and our contribution to it will remain the same.
Many companies are becoming more closed as they grow and grow.
But this approach is our free choice to make us more open.
and develop our business with the open source community. This means that everyone will be able to develop, contribute and test under equal conditions. There are no “community” or “enterprise” versions.

We do not pick up code from under the Apache 2.0 license. We just open it up even more.

We are supported by users

Elastic products have more than 200 million downloads, many people like our products.
We are working to ensure maximum usability, whether it be a public cloud, a private cloud, its own hardware, or a combination of all of the above.

We are trying to develop excellent technologies that you can trust in the future.

Are there any other questions?

We love good requests. Translator's note: query - search queries, pun
Here are the answers to a few common questions.

Are Elasticsearch, Kibana, Beats and Logstash still open-source?

Yes. we do not change licenses for existing Apache 2.0 code.
We just open the X-Pack code under a commercial license and add it to the appropriate repositories.

How now to contribute to the repositories of Elasticsearch, Kibana, Beats, and Logstash, if now there is code not under the Apache 2.0 license?

Just like before. The license of the contributor and the whole process remained unchanged.
The only thing that has changed is that now you can contribute to the X-Pack functionality.
Do you need an additional schedule or display to monitor Elasticsearch? Or improved Grok Debugger for Logstash? Now you can take part in creating / improving this functionality.

If the X-Pack code is now open, does this mean that it is now free?

Not. Many X-Pack features are free, such as monitoring, tile maps, Grok Debugger, and Search Profiler. Some X-Pack features are paid and require a license that is purchased with a gold or platinum subscription.

X-pack is now open source?

Open Source Licensing is clearly defined by the Open Source Initiative (OSI).

With version 6.3, the X-Pack code will be available under the Elastic License .

But it will not be in the traditional sense of 'Open Source' because Elastic License does not comply with the definition of OSI. However, the model of interaction with X-Pack code will be the same as for other open source Elastic products, including the ability to study code, create issues and pull requests in existing github repositories.