Zilliz
Security Posture
Compliance-ready
As of July 20, 2026, Zilliz's security: SOC 2 Type II, HIPAA, and ISO 27001 certifications alongside GDPR compliance and 11 controls including Encryption at Rest, Data Residency, and SSO mean regulated-industry procurement teams have the paperwork they typically require.
High confidence · 15 dated facts
Corroborated across multiple dated, sourced facts.
Corroborated across multiple dated, sourced facts.
Certifications
SOC 2 Type IIHIPAAISO 27001
Privacy
GDPR
Controls
Encryption At RESTData ResidencySSOSAMLRBACAudit LogsMFAEncryption In TransitPrivate NetworkingVPC PeeringIP Allowlisting
Security Change Historydated events · values unlock with a key
Security signal added: HIPAA · high significance
Security signal added: Data Residency · high significance
Security signal removed: Private Link · high significance
Security signal added: Data Residency · high significance
Security signal removed: CCPA · high significance
Security signal removed: HIPAA · high significance
Security signal removed: SCIM · high significance
Security signal added: VPC Peering · high significance
Every security fact on this pagekey · value · provenance · dated · sourced
| Fact | Value | Provenance | As of | Source |
|---|---|---|---|---|
| security.audit-logs | Audit Logs | company stated | 2026-07-20 | zilliz.com/pricing |
| security.cert.hipaa | HIPAA | company stated | 2026-07-20 | zilliz.com/trust-center |
| security.cert.iso-27001 | ISO 27001 | company stated | 2026-07-20 | zilliz.com/trust-center |
| security.cert.soc2-type-ii | SOC 2 Type II | company stated | 2026-07-20 | zilliz.com/trust-center |
| security.data-residency | Data Residency | company stated | 2026-07-20 | zilliz.com/trust-center |
| security.encryption-at-rest | Encryption At REST | company stated | 2026-07-20 | zilliz.com/trust-center |
| security.encryption-in-transit | Encryption In Transit | company stated | 2026-07-20 | zilliz.com/pricing |
| security.ip-allowlisting | IP Allowlisting | company stated | 2026-07-20 | zilliz.com/pricing |
| security.mfa | MFA | company stated | 2026-07-20 | zilliz.com/pricing |
| security.privacy.gdpr | GDPR | company stated | 2026-07-20 | zilliz.com/trust-center |
| security.private-networking | Private Networking | company stated | 2026-07-20 | zilliz.com/pricing |
| security.rbac | RBAC | company stated | 2026-07-20 | zilliz.com/pricing |
| security.saml | SAML | company stated | 2026-07-20 | zilliz.com/pricing |
| security.sso | SSO | company stated | 2026-07-20 | zilliz.com/pricing |
| security.vpc-peering | VPC Peering | company stated | 2026-07-20 | zilliz.com/pricing |
Security across Vector DatabasesZilliz ranked in place · tap through for each read
| Company | Security read | Facts |
|---|---|---|
| Pinecone | Compliance-ready | 19 |
| Turbopuffer | Compliance-ready | 17 |
| Zilliz this record | Compliance-ready | 15 |
| Qdrant | Baseline security | 12 |
| Vectara | Enterprise-grade | 12 |
| TopK | Compliance-ready | 8 |
| Activeloop | Baseline security | 5 |
| Epsilla | Baseline security | 3 |
No observed security facts yet for Chroma, KDB.AI, LanceDB, Marqo, Milvus, MyScale, Vespa and Weaviate.
Get security for zilliz.com via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/zilliz.com/facts?dimension=security
{
"data": {
"facts": [
{
"key": "security.cert.soc2-type-ii",
"value": true,
"provenance": "company_stated",
"as_of": "2026-07-20",
"source_url": "zilliz.com/trust-center"
},
{
"key": "security.cert.iso-27001",
"value": true,
"provenance": "company_stated",
"as_of": "2026-07-20",
"source_url": "zilliz.com/trust-center"
},
{
"key": "security.cert.hipaa",
"value": true,
"provenance": "company_stated",
"as_of": "2026-07-20",
"source_url": "zilliz.com/trust-center"
},
{
"key": "security.privacy.gdpr",
"value": true,
"provenance": "company_stated",
"as_of": "2026-07-20",
"source_url": "zilliz.com/trust-center"
},
"…"
]
}
}MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company_facts({ domain: "zilliz.com", dimension: "security" })
# returns the security record above,
# each value with its source_url + as_of,
# ready to reason overBuild on the company record. One key, REST + MCP, every signal dated and sourced back to the page it came from.
Public record, read from companies' own pages and boards. Every fact dated and sourced; provenance (observed vs company stated) shown inline.