Elastic
A recipe app for the founder’s wife became the context layer for enterprise AI.
In 2004, Shay Banon's wife was studying at Le Cordon Bleu in London, and he wanted to build her a recipe search app.
The infrastructure to do it properly didn't exist, so he built that instead. He quit his job and lived on his wife's income while he iterated toward a distributed search engine that could handle any application at any scale. He released it as Elasticsearch in 2010.
His wife is still waiting for the recipe app.
The highest lived stake in infrastructure
Banon didn't spot a market gap. He needed the tool, built it and watched the world adopt it. Of the infrastructure companies in this series, none scores higher on lived stake.
A friction that grew up
The friction has moved through three eras. In 2004 it was a missing open-source search engine. By 2012, enterprises were drowning in fragmented, expensive tools for searching their own data. Today, context has become the most important ingredient for enterprise AI. Every system that grounds a language model in a company's own information needs fast, accurate search across unstructured data.
An engine first built to search recipes is now the context layer for enterprise AI, and Elastic is calling itself the Search AI Company. FY25 revenue was $1.483 billion.
The 6.5
The aspiration Elastic has earned goes something like this: every enterprise AI application that needs to know what an organization knows will run on Elastic. That line isn't the front door. Neither is the recipe story, the most specific and human founding arc in enterprise infrastructure.
What would move the score
Lead with the recipe story as the origin of the context engine. Commission primary research on the context gap behind enterprise AI failures. Address the OpenSearch fork directly, since AWS forking Elasticsearch was itself evidence of how far ahead the technology was.
Want your own score? A Narrative Diagnostic runs your website, messaging and leadership content through the same four components.
