Elastic has announced changes in the way of licensing your software that will mean the abandonment of the Apache 2.0 license .

Rather than relying on the Apache Software Foundation license, the company will move source code from Elasticsearch and Kibana solutions to SSPL (Server Side Public License). This license created by MongoDB supports the use and modification without restrictions, as long as such modifications are published when delivering the product as a service, as well as the code of the management layers.

In this way, Elastic will give the option to choose between SSPL and its Elastic License . His intention is to get everything ready before the release of Elastic 7.11.

«Open source companies need to better protect their software to continue innovating and making the necessary investments,» says Shay Banon, the founder and CEO of Elastic, about this turnaround. «Some cloud service providers have taken open source products and delivered them as a service without investing back in the community.»

And there would be precisely the crux of the matter. Elastic names and points to practices carried out by Amazon Web Services (AWS) for some time.

«Over the past three years, the market has evolved and the community has come to appreciate that open source companies need to better protect their software to maintain a high level of investment and innovation,» insists Banon. «With the shift to SaaS as a delivery model, some cloud service providers have taken advantage of open source products «, in this case Elasticsearch and Kibana, « delivering them as a service without contributing . This diverts funds that would have been reinvested in the product and hurts users and the community, ”he reiterates.

Elastic goes further and explains that « AWS and Amazon Elasticsearch Service» have acted incorrectly «since 2015» .

“In the open source world, trademarks are considered an excellent and positive way to protect the reputation of the product”, declare Shay Banon. «They are considered sacred».

“So imagine our surprise when Amazon launched its Elasticsearch-based service in 2015 and called it Amazon Elasticsearch Service. We consider this to be a fairly obvious trademark infringement, ”he says. And he recalls that he himself applied for a personal loan in 2011 to register Elasticsearch, “believing in this standard of the open source ecosystem. Seeing the trademark so blatantly misused was especially painful for me, ”he says. «Our efforts to resolve the issue with Amazon failed, forcing us to file a lawsuit.»

AWS’s use of the brand “creates confusion among users who think that Amazon Elasticsearch Service is actually a service that is provided in conjunction with Elastic, with our blessing and collaboration. This is not true ”, she stresses.

And «when Amazon announced their Open Distro fork for Elasticsearch, they used code that we believe was copied by a third party from our commercial code and provided as part of the Open Distro project,» she complains. «This further divided our community and created more confusion.» And there would be more examples of «questionable ethical behavior.»

Elastic’s conclusion is that «Amazon’s behavior is inconsistent with the norms and values ​​that are especially important in the open source ecosystem.»

«We have tried all available avenues, including going through the courts, but with AWS’s continued behavior, we have decided to change our license so that we can focus on product creation and innovation rather than litigation,» says the CEO of Elastic. “The behavior of AWS has forced us to take this step and we do not do it lightly. If they had not acted as they have, we would not be discussing this issue today. ”

“If we don’t confront them now, as a successful, market-leading company, who will?” asks Banon. «Our hope is to take our market presence and use it to tackle now, so that others won’t face these same problems in the future «.

Elastic’s fight centers on Amazon’s cloud division. Meanwhile, he has managed to collaborate