Elastic cuts staff ~7% as CEO Ash Kulkarni says AI enables leaner teams

Elastic is trimming its workforce by an “approximately” 7% margin, and CEO Ash Kulkarni’s rationale is blunt: AI and automation are letting the company “operate with leaner teams.” In a blog post accompanying the layoffs, Kulkarni thanked employees for their hard work and said the customer-facing sales team would continue to grow, while other functions would shrink as the company shifts resources.

Here’s the immediate scale behind that “approximately” line. Elastic’s most recent SEC 10-K filing put total headcount at 4,019 employees. Slightly less than 300 Elasticians could be affected, depending on where the approximation lands. The same filing also matters because it frames what decision-makers are really looking at: not a vague “cost optimization,” but a concrete rebalancing of headcount across functions.

Elastic is also trying to turn the staffing story into an organizational one. Kulkarni said engineering, “where the nature of the work is evolving fastest,” will be split into three core areas, each led by a senior leader reporting directly to him. The idea is to simplify how the company operates, with fewer layers, less complexity, and less friction. In other words: this is not only about reducing the number of people. It is about changing how work gets divided, prioritized, and shipped, especially as the technology environment keeps shifting under teams tasked with search and analytics products.

The AI justification matters because it comes with a promise that the work still moves, but with different inputs. Kulkarni explicitly linked the layoffs to “advances in AI and automation” and said the company is “shifting our pace of innovation,” while also “investing in new skills.” That is a familiar script in tech right now, but the details are what executives pay attention to: Elastic is also planning to keep hiring in key strategic areas and locations, specifically including continued growth in customer-facing go-to-market functions. In the SEC 8-K filed last night, Elastic said it expects “total headcount to grow this fiscal year compared to last fiscal year.” So the company is not saying it will stop expanding overall. It is saying the expansion will be uneven across roles.

This is happening against a backdrop where Elastic has been fighting for control over how its software can be used and distributed. Elastic’s products include Elasticsearch and Kibana, where Elasticsearch is a distributed search and analytics engine and Kibana is a data visualization tool. In 2021, Elastic announced its adoption of the Server Side Public License (SSPL) to stop cloud providers from offering its software as a service. It had formerly used Apache 2.0, a more permissive license. The reaction was swift: Amazon Web Services (AWS) forked Elasticsearch and Kibana, calling the result OpenSearch, and later the OpenSearch project was transferred to the Linux Foundation.

Then Elastic added another licensing lever. In 2024, shortly before the OpenSearch transfer, Elastic announced that it was adding the GNU Affero General Public License v3 (AGPL) as an option. CTO Shay Banon said at the time, “I am so happy to be able to call Elasticsearch Open Source again.” That quote is notable because it shows Elastic’s constant pressure point: ensuring adoption while still managing strategic and competitive threats from forks and platform shifts.

So where does AI and automation fit into this bigger picture? From a governance and strategy standpoint, it looks like Elastic is responding to a changing labor economics and platform dynamics problem at the same time. If engineering is being reorganized and workloads are increasingly supported by automation, then the licensing history and competitive fork landscape becomes even more important. The company has to maintain product momentum, documentation, reliability, and adoption pressure in a world where cloud ecosystems can create near-parallel alternatives. Organizational clarity can be a competitive advantage. Headcount allocation becomes a mechanism to protect the areas the business believes will matter most next.

For boards and exec teams across the software industry, the second-order question is less “are they cutting headcount” and more “what does their future operating model look like, and who gets to stay in the driver seat?” Elastic’s plan indicates it expects AI-enabled productivity to change the structure of engineering, but it still wants growth in customer-facing go-to-market functions, and it expects overall headcount growth for the fiscal year compared to the last. That combination is a balancing act: deliver leaner teams internally without starving revenue-critical functions. And with engineering reporting directly to Kulkarni in three core areas, it also suggests a tighter management structure at the top, even while the company says it is reducing layers.

One more practical detail: The Register asked Elastic for a breakdown of the figures and said it will update if the company provides more information. That means the precise impact across departments is still to be clarified, but the headline numbers and the SEC filings already give decision-makers enough to model scenarios. If you are an executive in a similar business, Elastic’s move is a live case study in how AI narratives, restructuring, licensing legacy, and selective hiring can be combined in one announcement. The stakes are simple: get headcount and org design wrong, and you do not just cut costs. You slow the innovation engine while competitors keep shipping.