krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-05 10:58:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add details about differences between hybrid and private cloud

Browse Source
This commit is contained in:
Bastian Hofmann
2025-08-25 12:13:09 +02:00
parent be816d185d
commit 22a4667cbb
2 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/cloud-security.md
+5 -1
View File
@@ -32,6 +32,8 @@ Access to Qdrant Cloud accounts can be configured with granular [Role-Based Acce
For the Qdrant Hybrid Cloud management plane, the same security considerations as for the Managed Cloud apply. However, since the data plane is running in your own infrastructure, you are responsible for the security of the underlying infrastructure. For the Qdrant Hybrid Cloud management plane, the same security considerations as for the Managed Cloud apply. However, since the data plane is running in your own infrastructure, you are responsible for the security of the underlying infrastructure.
Hybrid Cloud was built for the most security minded organizations when "air gapped" is not a hard requirement it providers a similar developer and ops experience as Managed Cloud, while adhering to organizations overarching security protocols
Please refer to our [Hybrid Cloud documentation](/documentation/hybrid-cloud/) for more details. Please refer to our [Hybrid Cloud documentation](/documentation/hybrid-cloud/) for more details.
Qdrant clusters in Hybrid Cloud are also running in hardened containers with strict network policies. The databases are completely running on your infrastructure, within your network using your own controlled storage. Qdrant does not have any access to the database, the data in it, API keys, backups or to the database logs. Telemetry data and management instructions are shared with the Qdrant Cloud management plane. Qdrant clusters in Hybrid Cloud are also running in hardened containers with strict network policies. The databases are completely running on your infrastructure, within your network using your own controlled storage. Qdrant does not have any access to the database, the data in it, API keys, backups or to the database logs. Telemetry data and management instructions are shared with the Qdrant Cloud management plane.
@@ -40,7 +42,9 @@ Qdrant clusters in Hybrid Cloud are also running in hardened containers with str
In Qdrant Private Cloud, Qdrant clusters run completely isolated and air-gapped within your infrastucture without any connection to the Qdrant Cloud management plane. In Qdrant Private Cloud, Qdrant clusters run completely isolated and air-gapped within your infrastucture without any connection to the Qdrant Cloud management plane.
Please refer to our [Private Cloud documentation](/documentation/private-cloud/) for more details. Since no data or management instructions are shared with Qdrant, you are fully responsible for the security of the whole Qdrant Private Cloud installation. This also means that you do not benefit from all the integrated management and observability features of Qdrant Managed Cloud and Hybrid Cloud.
Please refer to our [Private Cloud documentation](/documentation/private-cloud/) for more details. We encourage you to weigh your security requirements against Hybrid Cloud before inquiring about Private Cloud.
Qdrant does not have any access to the database, the data in it, API keys, backups or to the database logs. No telemetry data is shared with Qdrant. Qdrant does not have any access to the database, the data in it, API keys, backups or to the database logs. No telemetry data is shared with Qdrant.
qdrant-landing/content/documentation/private-cloud/_index.md
+8
View File
@@ -18,4 +18,12 @@ On top of the open source Qdrant database, it allows
* Extended telemetry * Extended telemetry
* Qdrant Enterprise Support Services * Qdrant Enterprise Support Services
Since no data or management instructions are shared with Qdrant, you are fully responsible for the security of the whole Qdrant Private Cloud installation. This also means that you do not benefit from all the integrated management and observability features of Qdrant Managed Cloud and Hybrid Cloud, such as:
* A central management UI and API
* Integrated monitoring and alerting
* Configuration recommendations
We encourage you to weigh your security requirements against Hybrid Cloud before inquiring about Private Cloud.
If you are interested in using Qdrant Private Cloud, please [contact us](/contact-us/) for more information. If you are interested in using Qdrant Private Cloud, please [contact us](/contact-us/) for more information.