krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-06 11:28:31 +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:28 +02:00
committed by GitHub
co-authored by William Godfrey
parent 7b75084b43
commit 2761b546bc
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
@@ -44,7 +44,7 @@ Qdrant clusters in Hybrid Cloud also run in hardened, unprivileged containers wi
In Qdrant Private Cloud, Qdrant clusters run completely isolated and air-gapped within your infrastucture without any connection to the Qdrant Cloud Console.
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.
Since there is no connection or communication with Qdrant, you are fully responsible for the security of the entire Qdrant Private Cloud installation. This also means that you do not benefit from 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. 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.