Rank #5 of 5 in Search Infrastructure
Install
Showcase


Try itExperimental
See what an agent can do with Elasticsearch before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$docker run docker.elastic.co/elasticsearch/elasticsearch:9.5.3 (single-node, security off) # then index a doc + query q=name:infrastructure over HTTPrecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agent search — stories about agent search in this arenaAgent searchevidence →
Stories about agent search in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai search — stories about ai search in this arenaAi searchevidence →
Stories about ai search in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Developer experience — stories about developer experience in this arenaDeveloper experienceevidence →
Stories about developer experience in this arena
Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelinesevidence →
Stories about indexing pipelines in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Operations scale — stories about operations scale in this arenaOperations scaleevidence →
Stories about operations scale in this arena
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Relevance tuning — stories about relevance tuning in this arenaRelevance tuningevidence →
Stories about relevance tuning in this arena
Search experience — stories about search experience in this arenaSearch experienceevidence →
Stories about search experience in this arena
Security multitenancy — stories about security multitenancy in this arenaSecurity multitenancyevidence →
Stories about security multitenancy in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 2 free · 0 paid · 0 enterprise · 21 not stated in evidence
Follow the green: where the map greys out is where Elasticsearch stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent search — stories about agent search in this arenaAgent search
Stories about agent search in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~6/10
unlocks → Webhooks · Scoped API keys · Machine-readable spec · Versioning policy · Official CLI · API/UI parity · Full data export
Subscribe to events via webhooks
—–
Build against official SDKs
✓8/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
✓7/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~5/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
~3/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—0/10
Operate the product with natural-language commands
~6/10
unlocks → Autonomous automations
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
~4/10
Set up automations that run autonomously in the background
—–
Ai search — stories about ai search in this arenaAi search
Stories about ai search in this arena
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Developer experience — stories about developer experience in this arenaDeveloper experience
Stories about developer experience in this arena
Create an index, add documents, and run my first search within minutes of starting the quickstart
~6/10
Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more
~5/10
Official UI component libraries let me assemble a full search interface — box, results, facets, pagination — without building it from scratch
—–
Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines
Stories about indexing pipelines in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Operations scale — stories about operations scale in this arenaOperations scale
Stories about operations scale in this arena
Built-in analytics show top queries, no-result queries, and click-through so I know what users search for and miss
—–
Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents
~6/10
Self-host the full engine — same features as the hosted product — on my own infrastructure
!4/10
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Relevance tuning — stories about relevance tuning in this arenaRelevance tuning
Stories about relevance tuning in this arena
Search experience — stories about search experience in this arenaSearch experience
Stories about search experience in this arena
Security multitenancy — stories about security multitenancy in this arenaSecurity multitenancy
Stories about security multitenancy in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 3/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partialfree | 5/10 | Cclaimed | |
Run hybrid search — semantic vector similarity fused with keyword matching — in a single query C Hybrid | developer | Ai search — stories about ai search in this arenaAi search | 3 | full | 9/10 | Cclaimed | |
My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboard C Agent ops | ai-native user | Agent search — stories about agent search in this arenaAgent search | 3 | full | 8/10 | Tprobed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | fullfree | 8/10 | Xcommunity | |
Create an index, add documents, and run my first search within minutes of starting the quickstart C Onboarding | developer | Developer experience — stories about developer experience in this arenaDeveloper experience | 3 | partial | 6/10 | Xcommunity | |
Self-host the full engine — same features as the hosted product — on my own infrastructure G Self host | platform-engineer | Operations scale — stories about operations scale in this arenaOperations scale | 3 | disputed | 4/10 | Dcontradicted | |
Deliver as-you-type instant search with millisecond responses so results update on every keystroke C Experience | developer | Search experience — stories about search experience in this arenaSearch experience | 3 | none | 0/10 | ||
Published per-unit pricing (searches, records, or nodes) lets me predict what search will cost before committing G Pricing | founder | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 3 | none | 0/10 | ||
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | untested | none yet | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Searches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching applies C Experience | developer | Search experience — stories about search experience in this arenaSearch experience | 3 | none | untested | none yet | |
Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipeline C Hybrid | developer | Ai search — stories about ai search in this arenaAi search | 2 | full | 9/10 | Cclaimed | |
Agents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operations C Agent ops | ai-native user | Agent search — stories about agent search in this arenaAgent search | 2 | full | 7/10 | Tprobed | |
Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents C Scale | platform-engineer | Operations scale — stories about operations scale in this arenaOperations scale | 2 | partial | 6/10 | Xcommunity | |
Document adds, updates, and deletes become searchable in near real time without a full reindex C Ingestion | developer | Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines | 2 | partial | 5/10 | Xcommunity | |
Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more G Sdks | developer | Developer experience — stories about developer experience in this arenaDeveloper experience | 2 | partial | 5/10 | Cclaimed | |
Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single query C Filtering | developer | Search experience — stories about search experience in this arenaSearch experience | 2 | partial | 4/10 | Cclaimed | |
Costs stay predictable as records and query volume grow — no surprise per-request cliffs G Pricing | founder | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 2 | disputed | 4/10 | Dcontradicted | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 3/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | 0/10 | ||
Built-in analytics show top queries, no-result queries, and click-through so I know what users search for and miss C Analytics | founder | Operations scale — stories about operations scale in this arenaOperations scale | 2 | none | untested | none yet | |
Bulk-import millions of documents quickly, with async task tracking to know when indexing completes C Ingestion | platform-engineer | Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Define synonyms and curate results — pin, boost, or hide specific hits for specific queries C Curation | developer | Relevance tuning — stories about relevance tuning in this arenaRelevance tuning | 2 | none | untested | none yet | |
Official UI component libraries let me assemble a full search interface — box, results, facets, pagination — without building it from scratch C Ui libraries | developer | Developer experience — stories about developer experience in this arenaDeveloper experience | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Scoped or tenant tokens restrict each end user's searches to their own documents without separate indexes per user C Tenancy | developer | Security multitenancy — stories about security multitenancy in this arenaSecurity multitenancy | 2 | none | untested | none yet | |
Serve query suggestions and autocomplete backed by real search traffic or a suggestions index C Experience | developer | Search experience — stories about search experience in this arenaSearch experience | 2 | none | untested | none yet | |
Shape relevance with custom ranking rules and business signals (popularity, recency, margin) beyond textual matching C Ranking | developer | Relevance tuning — stories about relevance tuning in this arenaRelevance tuning | 2 | none | untested | none yet | |
Power RAG and conversational answers on top of my indexes with documented retrieval or answer APIs C Rag | developer | Ai search — stories about ai search in this arenaAi search | 1 | partial | 7/10 | Cclaimed | |
Ingest content with an official crawler or connectors instead of writing my own indexing pipeline C Connectors | founder | Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines | 1 | none | untested | none yet | |
Inspect ranking scores or explanations to understand exactly why a result ranked where it did C Ranking | platform-engineer | Relevance tuning — stories about relevance tuning in this arenaRelevance tuning | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 41 stories with headroom
What would move Elasticsearch’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
The evidence pack shows Elasticsearch's search/vector/RAG capabilities and an external MCP server for connecting AI agents to Elasticsearch, but nothing describes a built-in AI assistant embedded in the product that a user can delegate tasks to.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
The evidence pack contains no mention of Elasticsearch/Kibana alerting, Watcher, or any rule-based trigger-action automation for events; only search, vector, and serverless-scaling features are documented.
Search experience — stories about search experience in this arenaDeliver as-you-type instant search with millisecond responses so results update on every keystroke
nonemoves PA Scoreimpact 30
The evidence pack contains general marketing claims about speed ('unprecedented speed', '30x faster than Prom') and hybrid/vector search docs, but nothing describes autocomplete-style, keystroke-driven instant search (e.g.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Missing: any mention of data export APIs, snapshot/restore in open formats, or migration/exit tooling.
Pricing plans — plan structure and value — what each tier costs and what it unlocksPublished per-unit pricing (searches, records, or nodes) lets me predict what search will cost before committing
nonemoves PA Scoreimpact 30
No evidence of published per-unit pricing (per search, record, or node) anywhere in the pack; only vague marketing claims ('30x faster...
Search experience — stories about search experience in this arenaSearches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching applies
nonemoves PA Scoreimpact 30
The evidence pack focuses on vector/semantic/hybrid search, serverless deployment, and pricing/support commentary, but contains no mention of fuzzy matching, typo tolerance, or edit-distance/fuzziness query parameters that would support this story.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
Elasticsearch is a search/data engine, not an automation/orchestration platform; the evidence covers indexing, vector search, hybrid search, serverless scaling, and an MCP server for connecting agents to ES data, but nothing about scheduling or running autonomous background automations/workflows.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
The evidence pack mentions official client libraries (elastic-docs-6) and an MCP server (elastic-docs-28), but no official CLI tool tailored for AI-native/agentic workflows is documented anywhere in the pack.
Showing the top 8 of 41 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map7 surfaces · 22 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs20 stories
- My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboard
- Agents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operations
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Get AI-generated insights and suggestions from my data inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipeline
- Run hybrid search — semantic vector similarity fused with keyword matching — in a single query
- Power RAG and conversational answers on top of my indexes with documented retrieval or answer APIs
- Create an index, add documents, and run my first search within minutes of starting the quickstart
- Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more
- Self-host the core product
- Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents
- Self-host the full engine — same features as the hosted product — on my own infrastructure
- Costs stay predictable as records and query volume grow — no surprise per-request cliffs
- Choose where my data is stored (region/residency)
- Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single query
GitHub README7 stories
- My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboard
- Agents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operations
- Point an agent at llms.txt or agent-oriented docs
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Build against official SDKs
- Operate the product with natural-language commands
Hacker News6 stories
- Create an index, add documents, and run my first search within minutes of starting the quickstart
- Document adds, updates, and deletes become searchable in near real time without a full reindex
- Self-host the core product
- Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents
- Self-host the full engine — same features as the hosted product — on my own infrastructure
- Costs stay predictable as records and query volume grow — no surprise per-request cliffs
llms.txt2 stories
Cloud docs2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$docker run docker.elastic.co/elasticsearch/elasticsearch:9.5.3 (single-node, security off) # then index a doc + query q=name:infrastructure over HTTPreproduced$ docker run docker.elastic.co/elasticsearch/elasticsearch:9.5.3 (single-node, security off) # then index a doc + query q=name:infrastructure over HTTP
{"_index":"arenas","_id":"1","_version":1,"result":"created","forced_refresh":true,"_shards":{"total":2,"successful":1,"failed":0},"_seq_no":0,"_primary_term":1}
{"took":31,"timed_out":false,"_shards":{"total":1,"successful":1,"skipped":0,"failed":0},"hits":{"total":{"value":1,"relation":"eq"},"max_score":0.2876821,"hits":[{"_index":"arenas","_id":"1","_score":0.2876821,"_source":{"name":"search infrastructure arena"}}]}}
$printf '<jsonrpc initialize>' | ES_URL=http://127.0.0.1:9299 npx -y @elastic/mcp-server-elasticsearch # stdio handshake, no clusterreproduced$ printf '<jsonrpc initialize>' | ES_URL=http://127.0.0.1:9299 npx -y @elastic/mcp-server-elasticsearch # stdio handshake, no cluster
{"result":{"protocolVersion":"2025-06-18","capabilities":{"tools":{"listChanged":true}},"serverInfo":{"name":"elasticsearch-mcp","version":"0.3.1"}},"jsonrpc":"2.0","id":1}
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
4 of 9 testable claims verified · 1 contradicted → integrity 22/100
21 distinct capability claims found in Elasticsearch’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
4
Verified
4
Unverified
1
Contradicted
12
Undersold
Verified (6)
“Single shell command spins up a local Elasticsearch (and Kibana) instance for quickstart use”
Create an index, add documents, and run my first search within minutes of starting the quickstartpartialproof ↗
“Elastic Cloud Serverless auto-provisions, manages, and scales resources based on actual usage”
Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documentspartialproof ↗
“Official 'skills' packages teach AI coding agents how to work with Elasticsearch, Kibana, Fleet and the Elastic stack”
Point an agent at llms.txt or agent-oriented docspartialproof ↗
“Search and index tiers can be scaled independently with hardware optimized per workload”
Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documentspartialproof ↗
“Provides an official MCP server for Elasticsearch to connect AI agents”
“Autoscaling automatically allocates extra resources during short-term ingest spikes and scales back down afterward”
Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documentspartialproof ↗
Unverified (10)
“semantic_text fields auto-generate vector embeddings via a configured ML model on indexing”
Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipelinefullproof ↗
“Hybrid search runs full-text and vector search together in a single request”
Run hybrid search — semantic vector similarity fused with keyword matching — in a single queryfullproof ↗
“Recommends reciprocal rank fusion (RRF) to merge full-text and vector rankings for hybrid search”
Run hybrid search — semantic vector similarity fused with keyword matching — in a single queryfullproof ↗
“One engine combines vector search, full-text search, structured filters, aggregations, and hybrid retrieval”
Run hybrid search — semantic vector similarity fused with keyword matching — in a single queryfullproof ↗
“Wide range of official client libraries and developer tools across popular programming languages”
Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and morepartialproof ↗
“An inference API workflow gives finer control over configuring the embedding/inference endpoint”
Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipelinefullproof ↗
“Supports deploying external/hosted embedding models or bringing your own pre-computed vectors”
Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipelinefullproof ↗
“Supports building RAG (Retrieval Augmented Generation) systems on top of indexed data”
Power RAG and conversational answers on top of my indexes with documented retrieval or answer APIspartialproof ↗
“Functions as a vector database by storing embeddings in dense_vector or sparse_vector fields for similarity queries”
Run hybrid search — semantic vector similarity fused with keyword matching — in a single queryfullproof ↗
“Creating an index mapping alone enables ingesting, embedding, and querying without separate inference pipeline setup”
Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipelinefullproof ↗
Contradicted (1)
“Offers multiple self-managed and Elastic-managed deployment options”
Self-host the full engine — same features as the hosted product — on my own infrastructuredisputedproof ↗
Undersold (12)
My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboardfullproof ↗
Agents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operationsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIpartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Document adds, updates, and deletes become searchable in near real time without a full reindexpartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single querypartialproof ↗
Claims outside our story set (4)
Real capability claims found in Elasticsearch’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“New users can sign up for a free 14-day trial to create a serverless project”
source ↗“Cross-project search unifies visibility across isolated projects without moving or duplicating data”
source ↗“Improves vector quantization calibration speed during index merge operations”
source ↗“Audit events can now include raw request bodies for protobuf-based requests”
source ↗
Business model
AGPL-3.0 open-source engine (re-opened 2024), free to self-host; Elastic Cloud bills hosted deployments by resource tier and Serverless by usage, with a free trial and enterprise contracts.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
