Vector db project

contribute-docs/how-to/cumulative-docs/guidelines.md

@@ -304,7 +304,7 @@ For example, a page describing how to create an {{ech}} deployment just requires
 
 This is true for most situations. However, it can still be useful to call it out in a few specific scenarios:
 
-* **When there is a high risk of confusion for users**. For example, if a feature is available in two out of three serverless project types, it might make sense to clarify and be explicit about the feature being “unavailable” for the third type.
+* **When there is a high risk of confusion for users**. For example, if a feature is available in two out of four serverless project types, it might make sense to clarify and be explicit about the feature being “unavailable” for the other types.
 
   ```yml
   ---

deploy-manage/_snippets/cps-billing.md

@@ -4,7 +4,7 @@ When {{cps-init}} becomes generally available, charges are billed to the origin
 
 Usage is metered and charged based on the following factors:
 
-* **Retained data volume:** The volume of data retained in your linked projects each month. The rate varies by the type of each linked project, such as Observability, Security, or {{es}}. For Observability linked projects, the rate also depends on the type of retained data.
+* **Retained data volume:** The volume of data retained in your linked projects each month. The rate varies by the type of each linked project, such as Observability, Security, {{es}}, or {{es}} Vector Database. For Observability linked projects, the rate also depends on the type of retained data.
 * **{{cps-init}} queries:** Cross-project search queries incur a separate data egress charge for data transferred as a result of those queries. This appears as a separate line item on your bill.
 
 From August 1, 2026, the [Elastic Cloud Pricing](https://cloud.elastic.co/cloud-pricing-table) page shows detailed pricing for various {{cps}} scenarios.

deploy-manage/cloud-organization/billing.md

@@ -23,6 +23,7 @@ Elastic charges a recurring fee for using our offerings on {{ecloud}}. In this s
 * [](/deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md)
 * [](/deploy-manage/cloud-organization/billing/serverless-project-billing-dimensions.md)
   * [](/deploy-manage/cloud-organization/billing/elasticsearch-billing-dimensions.md)
+  * [](/deploy-manage/cloud-organization/billing/vector-database-billing-dimensions.md)
   * [](/deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md)
   * [](/deploy-manage/cloud-organization/billing/security-billing-dimensions.md)
 

deploy-manage/cloud-organization/billing/serverless-project-billing-dimensions.md

@@ -22,6 +22,7 @@ Specific prices can be found in the [Cloud Pricing Table](https://cloud.elastic.
 To learn about billing dimensions for specific offerings, refer to:
 
 * [](elasticsearch-billing-dimensions.md)
+* [](vector-database-billing-dimensions.md)
 * [](elastic-observability-billing-dimensions.md)
 * [](security-billing-dimensions.md)
 

deploy-manage/cloud-organization/billing/vector-database-billing-dimensions.md

@@ -0,0 +1,62 @@
+---
+navigation_title: Vector Database projects
+applies_to:
+  serverless: ga
+products:
+  - id: cloud-serverless
+  - id: serverless-vector-database
+description: >-
+  Learn how costs for Elasticsearch Vector Database Serverless projects
+  are calculated across storage, search, ingest, and infrastructure.
+---
+
+# {{es}} Vector Database billing dimensions [vector-database-billing]
+
+{{es}} Vector Database projects on {{serverless-full}} 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](/deploy-manage/deploy/elastic-cloud/project-settings.md#elasticsearch-manage-project-search-power-settings) 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](https://cloud.elastic.co/cloud-pricing-table?productType=serverless) or the [{{serverless-full}} pricing](https://www.elastic.co/pricing/serverless) pages.
+
+<!-- Fact-check: add a dedicated Vector Database pricing URL when marketing publishes one. -->
+
+## Storage [vector-database-billing-storage]
+
+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 [vector-database-billing-search]
+
+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](/deploy-manage/deploy/elastic-cloud/project-settings.md#elasticsearch-manage-project-search-power-settings) 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](https://cloud.elastic.co/cloud-pricing-table?productType=serverless).
+
+## Ingest [vector-database-billing-ingest]
+
+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.
+
+## Infrastructure [vector-database-billing-infrastructure]
+
+You are billed an hourly infrastructure fee for every hour that your project is running.
+
+## Managing Vector Database costs [vector-database-billing-managing-costs]
+
+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 setting [vector-database-billing-search-power-setting]
+
+[Search Power](/deploy-manage/deploy/elastic-cloud/project-settings.md#elasticsearch-manage-project-search-power-settings) 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.
+
+## Related billing dimensions [vector-database-billing-related]
+
+Shared {{serverless-short}} add-ons such as [data out](serverless-project-billing-dimensions.md#general-serverless-billing-data-out) and [support](serverless-project-billing-dimensions.md#general-serverless-billing-support) may also appear on your bill. See [](serverless-project-billing-dimensions.md).
+
+If you use {{cps}}, additional charges may apply when the feature becomes generally available. For how those charges are calculated, refer to [ {{cps}} Billing](/deploy-manage/cross-project-search-config.md#cps-billing).

deploy-manage/cross-project-search-config.md

@@ -58,7 +58,7 @@ During technical preview, only newly created projects can be origin projects for
 To be available for linking, projects must meet the following requirements:
 
 - The origin project and all linked projects must be in the same {{ecloud}} organization.
-- You can link any combination of {{product.elasticsearch}}, {{product.observability}}, and {{product.security}} projects in the same organization.
+- You can link any combination of {{product.elasticsearch}}, {{es}} Vector Database, {{product.observability}}, and {{product.security}} projects in the same organization.
 - Projects can be linked across cloud providers and regions. For example, a project in GCP `us-east4` can be linked to a project in AWS `eu-central-1` without any additional configuration.
 - {{sec-serverless}} and {{obs-serverless}} projects require the **Complete** feature tier. Projects on the **Essentials** tier are not compatible with {{cps}}.
 
@@ -75,7 +75,16 @@ For most deployments, we recommend creating a dedicated **overview project** tha
 
 In this architecture, you create a new, empty project and link existing projects to it. You run all cross-project searches from the new overview project, while your actual active projects continue to operate independently. The linked ("spoke") projects are not linked to each other.
 
-![Overview project architecture for cross-project search](images/serverless-cross-project-search-arch.svg)
+```mermaid
+flowchart TB
+    O["Overview project<br/>Origin (empty hub)"]
+    O --> S["Security project<br/>Linked (data)"]
+    O --> Obs["Observability project<br/>Linked (data)"]
+    O --> E["Elasticsearch project<br/>Linked (data)"]
+    O --> V["Vector Database project<br/>Linked (data)"]
+```
+
+Searches run from the overview project across all linked projects. Linked projects operate independently and are not linked to each other. You can link any combination of compatible projects.
 
 The overview project becomes a central point for broad searches, dashboards, and investigations, without affecting your existing setup.
 

deploy-manage/deploy/elastic-cloud/create-an-organization.md

@@ -34,11 +34,12 @@ A deployment lets you explore Elastic solutions for Search, Observability, and S
 
 For more information, check the [{{ech}} documentation](cloud-hosted.md).
 
-**Three {{serverless-short}} projects**
+**Four {{serverless-short}} project types**
 
 {{serverless-short}} projects package {{stack}} features by type of solution:
 
 * [{{es}}](../../../solutions/search.md)
+* [{{es}} Vector Database](/solutions/vector-database.md)
 * [Observability](../../../solutions/observability.md)
 * [Security](../../../solutions/security.md)
 

deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md

@@ -25,7 +25,7 @@ The following information reflects our strategic goals, plans and objectives and
 | **Functionality** | {{ech}} | {{serverless-full}} |
 |--------|----------------------|--------------------------|
 | **Management model** | Self-service infrastructure | Fully managed service |
-| **Project organization** | Single deployments with multiple capabilities | Separate projects for Elasticsearch, Observability, and Security |
+| **Project organization** | Single deployments with multiple capabilities | Separate projects for Elasticsearch, Elasticsearch Vector Database, Observability, and Security |
 | **Scaling** | Manual or automated with configuration | Fully automated |
 | **Infrastructure decisions** | User manages capacity | Automatically managed by Elastic |
 | **Pricing model** | Based on provisioned resources | Based on usage |

deploy-manage/deploy/elastic-cloud/project-settings.md

@@ -54,6 +54,7 @@ $$$elasticsearch-manage-project-search-power-settings$$$
 | Setting | Description | Project Type |
 | :--- | :--- | :--- |
 | **Search Power** | Search Power controls the amount of baseline resources kept ready for your data and the maximum amount of resources the system can allocate to your project under high search load.<br><br>Increase **Search Power** to add resources for improved query throughput and performance as load increases. Decrease it to reduce the amount of provisioned resources, which lowers both active search costs and the reduced rate billed during idle periods, at the cost of more variable query latency. The On-demand setting provides the lowest baseline and idle cost.<br><br>Choose from three Search Power settings:<br><br>**On-demand:** Low cost option. Query latency is variable and maximum throughput is limited, particularly during demand spikes.<br><br>**Performant:** Delivers low _average_ query latency with no practical query throughput limits to meet varying demand.<br><br>**High availability:** Maintains consistent low query latency across most search workloads, from steady baseline to peak demand.<br> | {{es}} |
+| **Search Power** | Search Power reserves search capacity for your project. Unlike {{es}} projects, capacity is not scaled automatically based on query load.<br><br>The default value is **100**, which reserves enough search resources so that 100% of your project data remains available for low-latency search. You can increase Search Power in increments of 100. Higher values reserve proportionally more capacity: for example, **200** reserves about twice the capacity of **100**. You can increase Search Power up to **1900**.<br> | {{es}} Vector Database |
 | **Search Boost Window** | Non-time series data is always considered search-ready. The **Search Boost Window** determines the volume of time series project data that will be considered search-ready.<br><br>Increasing the window results in a bigger portion of time series project data included in the total search-ready data volume.<br> | {{es}} |
 | **Data Retention** | Data retention policies determine how long your project data is retained.<br>In {{serverless-full}} data retention policies are configured through [data streams](../../../manage-data/lifecycle/data-stream.md) and you can [specify different retention periods](../../../manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md#set-lifecycle) for specific data streams in your project.<br><br> {{elastic-sec}} has two additional configuration settings that can be configured to manage your data retention.<br><br>**Maximum data retention period**<br><br>When enabled, this setting determines the maximum length of time that data can be retained in any data streams of this project.<br><br>Editing this setting replaces the data retention set for all data streams of the project that have a longer data retention defined. Data older than the new maximum retention period that you set is permanently deleted.<br><br> **Default data retention period**<br><br>When enabled, this setting determines the default retention period that is automatically applied to all data streams in your project that do not have a custom retention period already set.<br> |Elasticsearch<br>Observability<br>Security  |
 | **Project features** | Controls [feature tiers and add-on options](../../../deploy-manage/deploy/elastic-cloud/project-settings.md#project-features-add-ons) for your {{elastic-sec}} project. | Security |

deploy-manage/deploy/elastic-cloud/serverless.md

@@ -25,9 +25,10 @@ There are differences between {{es-serverless}} and {{ech}}. Learn more in [Comp
 
 ## Get started
 
-Elastic provides three serverless solutions available on {{ecloud}}. Follow these guides to get started with your serverless project:
+Elastic provides four serverless project types available on {{ecloud}}. Follow these guides to get started with your serverless project:
 
-* **[{{es-serverless}}](/solutions/search/get-started.md)**: Build powerful applications and search experiences using a rich ecosystem of vector search capabilities, APIs, and libraries.
+* **[{{es-serverless}}](/solutions/search/get-started.md)**: Build powerful, scalable search and analytics applications across structured data, logs, metrics, documents, and vectors as part of a broader {{stack}}.
+* **[{{es}} Vector Database](/solutions/vector-database/get-started.md)**: Build embedding-driven workloads such as semantic search, RAG, and AI-powered retrieval. Built-in models, `semantic_text`, and vector-optimized defaults mean less configuration and faster time to production.
 * **[{{obs-serverless}}](../../../solutions/observability/get-started.md)**: Monitor your own platforms and services using powerful machine learning and analytics tools with your logs, metrics, traces, and APM data.
 * **[{{sec-serverless}}](../../../solutions/security/get-started.md#create-sec-serverless-project)**: Detect, investigate, and respond to threats with SIEM, endpoint protection, and AI-powered analytics capabilities.
 

deploy-manage/toc.yml

@@ -821,6 +821,7 @@ toc:
           - file: cloud-organization/billing/serverless-project-billing-dimensions.md
             children:
               - file: cloud-organization/billing/elasticsearch-billing-dimensions.md
+              - file: cloud-organization/billing/vector-database-billing-dimensions.md
               - file: cloud-organization/billing/elastic-observability-billing-dimensions.md
               - file: cloud-organization/billing/security-billing-dimensions.md
           - file: cloud-organization/billing/billing-models.md

deploy-manage/users-roles/cloud-organization/user-roles.md

@@ -130,9 +130,9 @@ You can optionally [create custom roles in a project](/deploy-manage/users-roles
 
 | Role name | {{ecloud}} access | Project access | Availability |
 | --- | --- | --- | --- |
-| Admin | Has full access to project management, properties, and security privileges. | Superuser role privileges | [![{{es}}](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md)[![{{observability}}](/deploy-manage/images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security.md) |
-| Developer | Manage project settings. | Creates API keys, indices, data streams, adds connectors, and builds visualizations. | [![{{es}}](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md) |
-| Viewer | Has read-only access to project details. | Has read-only access to project data and features. | [![{{es}}](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md)[![{{observability}}](/deploy-manage/images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security.md) |
+| Admin | Has full access to project management, properties, and security privileges. | Superuser role privileges | [![{{es}}](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Vector Database](/deploy-manage/images/serverless-vectordb-badge.svg "")](../../../solutions/vector-database.md)[![{{observability}}](/deploy-manage/images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security.md) |
+| Developer | Manage project settings. | Creates API keys, indices, data streams, adds connectors, and builds visualizations. | [![{{es}}](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Vector Database](/deploy-manage/images/serverless-vectordb-badge.svg "")](../../../solutions/vector-database.md) |
+| Viewer | Has read-only access to project details. | Has read-only access to project data and features. | [![{{es}}](/deploy-manage/images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Vector Database](/deploy-manage/images/serverless-vectordb-badge.svg "")](../../../solutions/vector-database.md)[![{{observability}}](/deploy-manage/images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security.md) |
 | Editor | Configures all {{observability}} or Security projects. | Has read-only access to data indices. Has full access to all project features. | [![{{observability}}](/deploy-manage/images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security.md) |
 | Tier 1 analyst | Viewer | Ideal for initial alert triage. General read access, can create dashboards and visualizations. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security.md) |
 | Tier 2 analyst | Viewer | Ideal for alert triage and beginning the investigation process. Can create cases. | [![Security](/deploy-manage/images/serverless-sec-badge.svg "")](../../../solutions/security.md) |