We recently announced a license change: Blog, FAQ. We posted some additional guidance on the license change this morning. I wanted to share why we had to make this change. This was an incredibly hard decision, especially with my background and history around Open Source. I take our responsibility very seriously. And to be clear, this change most likely has zero effect on you, our users. It has no effect on our customers that engage with us either in cloud or on premises.

We are moving our Apache 2.0-licensed source code in Elasticsearch and Kibana to be dual licensed under Server Side Public License (SSPL) and the Elastic License, giving users the choice of which license to apply. This license change ensures our community and customers have free and open access to use, modify, redistribute, and collaborate on the code.

Elastic solutions solve many different business challenges from powering search bars to creating observable systems to detecting and responding to threats. And with the amount of capabilities each offers, learning how to maximize the power of our solutions for enterprise search, observability, and security is critical to realizing Elastic's full value. But finding the time to build new skills can be challenging.

Indexing the web is hard. There’s a nearly infinite supply of misbehaving sites, misapplied (or ignored) standards, duplicate content, and corner cases to contend with. It’s a big task to create an easy-to-use web crawler that’s thorough and flexible enough to account for all the different content it encounters.

Elastic Cloud puts the power of the Elastic Stack in your hands within minutes. Whether you’re trying to add search capabilities with Elastic Enterprise Search, monitor critical systems and applications with Elastic Observability, or protect your organization from cyber threats with Elastic Security, taking the first step is easy.

Today’s cars are computers on wheels, and they’re powered by software as much as they are by batteries or gasoline. When it comes to building software for Audi, Volskwagen, Porsche, Traton, and other brands, that’s a task assigned to Audi Business Innovation (ABI). “Developers need the right tools in their hands that are easy to use,” says Stefan Teubner, an ABI team leader and DevOps engineer.

We created the Elastic Contributor Program to encourage knowledge sharing in our community and to recognize and reward the hard work of our awesome contributors. There are six different contribution types accepted in the program: event organization, presentation, written content, video, translation, and code. In this blog post, we’ll cover how to contribute code in the many free and open projects that Elastic maintains.

Increasingly, we are seeing on-prem workloads being moved onto the cloud. Elasticsearch has been around for many years with our users and customers typically managing it themselves on-prem. Elasticsearch Service on Elastic Cloud — our managed Elasticsearch service that runs on Amazon Web Services (AWS), Google Cloud, and Microsoft Azure across many different regions, is the best way to consume the Elastic Stack and our solutions for enterprise search, observability, and security.

With Elastic 7.9, the Elastic Agent and Fleet were released, along with a new way to structure indices and data streams in Elasticsearch for time series data. In this blog post, we'll give an overview of the Elastic data stream naming scheme and how it works. This is the first in a series of blog posts around the Elastic data stream naming scheme.

Many users need their Elasticsearch clusters to always be available. And a lot of these same users also want to upgrade their Elasticsearch environment when a new version is released, so they can take advantage of all the new features and functionality. The result is that admins end up upgrading the Elasticsearch engine while it is operating at full capacity in production. Sound too good to be true?