Elasticsearch Vector Database billing dimensions

Elasticsearch Vector Database projects on Elastic Cloud Serverless are priced based on consumption across storage, search, ingest, and infrastructure.

Your monthly bill is calculated based on these components:

• Storage — Measured by the total amount of data stored in your project, in GB.
• Search — Measured by reserved search capacity for your stored data. Capacity is controlled by your project's Search Power setting and scales with how much data you store.
• Ingest — Measured by the volume of data you ingest into your project over the course of a month, in GB.
• Infrastructure fee — Measured by the number of hours your project is running.

For current rates, refer to the Cloud Pricing Table or the Elastic Cloud Serverless pricing pages.

You are charged per GB of data stored in the project. Storage charges apply for as long as the data remains in the project.

Search charges cover the search capacity reserved for your stored data. All stored data is searchable by default, which means it actively contributes to Search charges.

Search Power determines how much capacity is reserved. At Search Power 100, enough capacity is reserved so that 100% of your project data remains available for low-latency search. Higher Search Power values reserve more capacity in proportion to that baseline: for example, 200 reserves about twice as much as 100.

Increasing Search Power reserves more capacity and raises search charges. Running more queries does not increase search charges. For current rates, refer to the Cloud Pricing Table.

Ingest charges are based on the volume of data written to your project, measured in GB for the billing period. This uses the same definition of billable ingested bytes as other Serverless offerings.

You are billed an hourly infrastructure fee for every hour that your project is running.

Vector Database costs follow your storage footprint, search resource allocation, ingest volume, and the hours your project is available. To balance performance with spend, adjust the controls described in this section.

Search Power reserves search capacity for your project. Start at the default of 100, measure latency and throughput for your workload, then increase Search Power if you need more capacity. You increase Search Power in increments of 100. Higher Search Power increases search charges in proportion to the setting and your stored data volume. You can increase Search Power up to 1900.

For high availability, you can increase Search Power to 200. That setting reserves enough capacity for two full copies of your project data to remain available for low-latency search.

Shared Serverless add-ons such as data out and support may also appear on your bill. See Serverless project billing dimensions.

If you use cross-project search, additional charges may apply when the feature becomes generally available. For how those charges are calculated, refer to cross-project search Billing.