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 your project's active storage.
• Ingest - Measured by the volume of data you ingest into your project over the course of a month, in GB.
• Infrastructure fee - A recurring project fee. Usage is metered by the hour for as long as the project exists, so a full month looks like a flat monthly charge and partial months are pro-rated.

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. Each Vector Database project can store up to 1 TB of data.

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

Search charges scale with Search Power and your project's active storage. Active storage is the volume of data used as the basis for search billing. For billing, active storage has a 16 GB minimum: if your project stores less than 16 GB, search charges still use 16 GB as the storage basis.

At Search Power 100, capacity is reserved to keep the project's full dataset available for low-latency search. Increasing Search Power does not increase the amount of data covered. Instead, it reserves additional search capacity for the same dataset, which can improve performance for higher query concurrency or more demanding search workloads.

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 infrastructure fee for as long as the project exists. Elastic meters this fee by the hour, so on your bill it behaves like a monthly project fee that is pro-rated if you create or delete the project mid-month.

There is no separate control to pause or make a project unavailable. To stop infrastructure charges, delete the project.

Vector Database costs follow your storage footprint, search resource allocation, ingest volume, and the infrastructure fee for the time your project exists. 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 active storage. You can increase Search Power up to 1900.

Shared Serverless add-ons such as data out and support may also appear on your bill. Refer to 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.