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

Update qdrant-landing/content/documentation/cloud-security.md

Browse Source 
Co-authored-by: William Godfrey <will@catalyst-tech.io>
This commit is contained in:
Bastian Hofmann
2025-08-26 16:20:12 +02:00
committed by GitHub
co-authored by William Godfrey
parent db410cdee9
commit 7b75084b43
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/cloud-security.md
+1 -1
View File
@@ -46,7 +46,7 @@ In Qdrant Private Cloud, Qdrant clusters run completely isolated and air-gapped
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.
Please refer to our [Private Cloud documentation](/documentation/private-cloud/) for more details. As Private Cloud is completely isolated from the Qdrant Cloud Console, we encourage you to assess your security requirements against Hybrid Cloud before considering Private Cloud for the best experience.
With Private Cloud, Qdrant has no access to the database, any stored data, API keys, backups or the cluster logs. Compared to Hybrid Cloud, telemetry data is not shared with Qdrant and it is not possible to use the Qdrant Cloud Console to manage your clusters.