Merge pull request #2128 from qdrant/feat/bashofmann/iops-docs

Enhance cluster creation documentation with disk speed options, including recommendations

qdrant-landing/content/documentation/cloud/create-cluster.md

@@ -82,6 +82,8 @@ This page shows you how to use the Qdrant Cloud Console to create a custom Qdran
    > Each node is automatically attached with a disk, that has enough space to store data with Qdrant's default collection configuration.
 1. Select additional disk space for your deployment.
    > Depending on your collection configuration, you may need more disk space per RAM. For example, if you configure `on_disk: true` and only use RAM for caching. 
+1. Choose the speed tier for your disk. (AWS only)
+   > Higher speed tiers provide better performance, especially for write-heavy workloads, or configurations with a low RAM cache ratio.
 1. Review your cluster configuration and pricing.
 1. When you're ready, select **Create**. It takes some time to provision your cluster.
 
@@ -99,6 +101,10 @@ To create a production-ready cluster, you need to ensure the following:
 
 Your cluster should have at least 3 nodes, and each collection should have a replication factor of at least 2. This ensures that is one node fails, or is restarted due to maintenance, a version upgrade, or a scaling operation, that the cluster remains fully operational. You can ensure this by checking the **High Availability** checkbox when creating a cluster.
 
+**Disk Speed (AWS only)**
+
+We recommend the **Balanced** tier for disks >= 32 GiB, and the **Performance** tier for disks >= 256 GiB.
+
 **Backup and Disaster Recovery**
 
 You should create a backup schedule for your cluster. This ensures that you can restore your data in case of a disaster. You can configure backups in the **Backups** section of the cluster detail page. See [**Backups**](/documentation/cloud/backups/) for more information.

qdrant-landing/content/documentation/cloud/inference.md

@@ -35,11 +35,12 @@ Inference is billed based on the number of tokens processed by the model. The co
 
 ## Use External Models
 
-Qdrant Cloud can act as a proxy for the APIs of three external embedding model providers:
+Qdrant Cloud can act as a proxy for the following external embedding providers:
 
 - OpenAI
 - Cohere
 - Jina AI
+- OpenRouter
 
 This enables you to access any of the embedding models provided by these providers through the Qdrant API.
 

qdrant-landing/content/documentation/hybrid-cloud/_index.md

@@ -24,9 +24,7 @@ Qdrant Hybrid Cloud ensures data privacy, deployment flexibility, low latency, a
 
 The Hybrid Cloud onboarding will install a Kubernetes Operator, a Cloud Agent and a Prometheus Agent into your Kubernetes cluster.
 
-and do not include any user data or sensitive information.
-
-Both the Cloud Agent will establish an outgoing connection to `cloud.qdrant.io` on port `443` to transport telemetry and receive management instructions. It will also interact with the Kubernetes API through a ServiceAccount to create, read, update and delete the necessary Qdrant CRs (Custom Resources) based on the configuration setup in the Qdrant Cloud Console.
+Both the Cloud Agent and the Prometheus Agent will establish an outgoing connection to `cloud.qdrant.io` on port `443` to transport telemetry and receive management instructions. It will also interact with the Kubernetes API through a ServiceAccount to create, read, update and delete the necessary Qdrant CRs (Custom Resources) based on the configuration setup in the Qdrant Cloud Console.
 
 The Qdrant Kubernetes Operator will manage the Qdrant databases within your Kubernetes cluster. Based on the Qdrant CRs, it will interact with the Kubernetes API through a ServiceAccount to create and manage the necessary resources to deploy and run Qdrant databases, such as Pods, Services, ConfigMaps, and Secrets.