mirror of
https://github.com/qdrant/landing_page.git
synced 2026-09-30 16:38:31 +02:00
Add docs for private cloud and premium tier
This commit is contained in:
@@ -3,7 +3,7 @@ title: Authentication
|
||||
weight: 30
|
||||
---
|
||||
|
||||
# Authenticating to Qdrant Cloud
|
||||
# Database Authentication in Qdrant Managed Cloud
|
||||
|
||||
This page shows you how to use the Qdrant Cloud Console to create a custom API key for a cluster. You will learn how to connect to your cluster using the new API key.
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@ In this case vectors will be stored on the disc in memory-mapped files, and only
|
||||
The amount of available RAM will significantly affect the performance of the search.
|
||||
As a rule of thumb, if you keep 2 times less vectors in RAM, the search latency will be 2 times lower.
|
||||
|
||||
The speed of disks is also important. [Let us know](mailto:cloud@qdrant.io) if you have special requirements for a high-volume search.
|
||||
The speed of disks is also important. [Let us know](/documentation/support/) if you have special requirements for a high-volume search.
|
||||
|
||||
## Sub-groups oriented configuration
|
||||
|
||||
|
||||
@@ -37,4 +37,4 @@ Note, that it is currently not possible to horizontally scale down the cluster i
|
||||
|
||||
We will be glad to consult you on an optimal strategy for scaling.
|
||||
|
||||
[Let us know](mailto:cloud@qdrant.io) your needs and decide together on a proper solution.
|
||||
[Let us know](/documentation/support/) your needs and decide together on a proper solution.
|
||||
|
||||
@@ -0,0 +1,17 @@
|
||||
---
|
||||
title: Premium Tier
|
||||
weight: 66
|
||||
---
|
||||
|
||||
# Qdrant Cloud Premium Tier
|
||||
|
||||
Qdrant Cloud offers an optional premium tier for customers who require additional features and better SLA support levels. The premium tier includes:
|
||||
|
||||
* **24/7 Support**: Our support team is available around the clock to help you with any issues you may encounter.
|
||||
* **Shorter Response Times**: Premium customers receive priority support and can expect faster response times, with shorter SLAs.
|
||||
* **99.9% Uptime SLA**: We guarantee 99.9% uptime for your Qdrant Cloud clusters.
|
||||
* **Single Sign-On (SSO)**: Premium customers can use their existing SSO provider to manage access to Qdrant Cloud.
|
||||
* **VPC Private Links**: Premium customers can connect their Qdrant Cloud clusters to their VPCs using private links (AWS only).
|
||||
* **Storage encryption with shared keys**: Premium customers can encrypt their data at rest using their own keys (AWS only).
|
||||
|
||||
If you are interested in using switch to Qdrant Cloud Premium, please [contact us](/contact-us/) for more information.
|
||||
@@ -52,3 +52,19 @@ If you use multiple accounts for different purposes, it is a good idea to give t
|
||||
### Deleting an account
|
||||
|
||||
When you delete an account, all database clusters and associated data will be deleted.
|
||||
|
||||
## Enterprise Single-Sign-On (SSO)
|
||||
|
||||
Qdrant Cloud supports Enterprise Single-Sign-On for Premium Tier customers. The following providers are supported:
|
||||
|
||||
* Active Directory/LDAP
|
||||
* ADFS
|
||||
* Azure Active Directory Native
|
||||
* Google Workspace
|
||||
* OpenID Connect
|
||||
* Okta
|
||||
* PingFederate
|
||||
* SAML
|
||||
* Azure Active Directory
|
||||
|
||||
Enterprise Sign-On is available as an add-on for [Premium Tier](/documentation/cloud/premium/) customers. If you are interested in using SSO, please [contact us](/contact-us/).
|
||||
@@ -1,15 +0,0 @@
|
||||
---
|
||||
title: Cloud Support
|
||||
weight: 99
|
||||
aliases:
|
||||
---
|
||||
|
||||
# Qdrant Cloud Support and Troubleshooting
|
||||
|
||||
All Qdrant Cloud users are welcome to join our [Discord community](https://qdrant.to/discord/). Our Support Engineers are available to help you anytime.
|
||||
|
||||

|
||||
|
||||
Paid customers can also contact support directly. Links to the support portal are available in the Qdrant Cloud Console.
|
||||
|
||||

|
||||
Reference in New Issue
Block a user