Skip to content

Refine the explanation of EIS billing per MToks. #4034

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Nov 21, 2025
+1 −1
Merged

Refine the explanation of EIS billing per MToks. #4034

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8b7bfa8
Refine the explanation of EIS billing per MToks.
seanhandley Nov 21, 2025
8316eb6
Update deploy-manage/cloud-organization/billing/elasticsearch-billing…
seanhandley Nov 21, 2025
7a5c11b
Further edits for grammar and clarity.
seanhandley Nov 21, 2025
bff0457
Update deploy-manage/cloud-organization/billing/elasticsearch-billing…
seanhandley Nov 21, 2025
51871cf
Merge branch 'main' into seanh/refine-billing-dimensions-for-eis
shainaraskas Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ For detailed {{es-serverless}} project rates, refer to the [{{es-serverless}} pr
* **Indexing:** The VCUs used to index incoming documents. Indexing VCUs account for compute resources consumed for ingestion. This is based on ingestion rate and amount of data ingested at any given time. Transforms and ingest pipelines also contribute to ingest VCU consumption.
* **Search:** The VCUs used to return search results with the latency and queries per second (QPS) you require. Search VCUs are calculated as a factor of the compute resources needed to run search queries, search throughput, and latency. Search VCUs are not charged per search request. Instead, they are a factor of the compute resources that scale up and down based on amount of searchable data, search load (QPS), and performance (latency and availability).
* **Machine learning:** The VCUs used to perform inference, NLP tasks, and other ML activities. ML VCUs are a factor of the models deployed and number of ML operations such as inference for search and ingest. ML VCUs are typically consumed for generating embeddings during ingestion and during semantic search or reranking.
* **Tokens:** The Elastic Managed LLM is charged per 1 million input and output tokens. The LLM powers all AI Search features such as Playground and AI Assistant for Search and is enabled by default.
* **Tokens:** [The Elastic Inference Service](https://www.elastic.co/docs/explore-analyze/elastic-inference/eis) is charged based on tokens used with machine learning models. For embeddings/reranker models, this is per million input tokens. For LLMs this is per 1 million input or output tokens. Elastic Managed LLMs can power all AI Search features (such as Playground and AI Assistant for Search), features in the Security and Observability Products, and is enabled by default.

## Data storage and billing [elasticsearch-billing-information-about-the-search-ai-lake-dimension-gb]

Expand Down
Loading