TopK
Security Posture
Compliance-ready
As of July 20, 2026, TopK's security: SOC 2 and SOC 2 Type I are listed, alongside encryption in transit, encryption at rest, and RBAC; enterprise procurement teams will likely ask for Type II, which is not yet listed.
High confidence · 8 dated facts
Corroborated across multiple dated, sourced facts.
Corroborated across multiple dated, sourced facts.
Certifications
SOC 2SOC 2 Type I
Controls
Encryption In TransitEncryption At RESTRBACAudit LogsVPC PeeringData Residency
Security Change Historydated events · values unlock with a key
Security signal added: VPC Peering · high significance
Security signal removed: Private Networking · high significance
Security signal removed: Private Networking · high significance
Security signal added: Data Residency · high significance
Security signal added: SOC 2 · 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 | docs.topk.io |
| security.cert.soc2 | SOC 2 | company stated | 2026-07-20 | www.topk.io/security |
| security.cert.soc2-type-i | SOC 2 Type I | company stated | 2026-07-20 | docs.topk.io |
| security.data-residency | Data Residency | company stated | 2026-07-20 | docs.topk.io |
| security.encryption-at-rest | Encryption At REST | company stated | 2026-07-20 | docs.topk.io |
| security.encryption-in-transit | Encryption In Transit | company stated | 2026-07-20 | docs.topk.io |
| security.rbac | RBAC | company stated | 2026-07-20 | docs.topk.io |
| security.vpc-peering | VPC Peering | company stated | 2026-07-20 | docs.topk.io |
Security across Vector DatabasesTopK ranked in place · tap through for each read
| Company | Security read | Facts |
|---|---|---|
| Pinecone | Compliance-ready | 19 |
| Turbopuffer | Compliance-ready | 17 |
| Zilliz | Compliance-ready | 15 |
| Qdrant | Baseline security | 12 |
| Vectara | Enterprise-grade | 12 |
| TopK this record | 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 topk.io via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/topk.io/facts?dimension=security
{
"data": {
"facts": [
{
"key": "security.cert.soc2",
"value": true,
"provenance": "company_stated",
"as_of": "2026-07-20",
"source_url": "www.topk.io/security"
},
{
"key": "security.cert.soc2-type-i",
"value": true,
"provenance": "company_stated",
"as_of": "2026-07-20",
"source_url": "docs.topk.io"
},
{
"key": "security.encryption-in-transit",
"value": true,
"provenance": "company_stated",
"as_of": "2026-07-20",
"source_url": "docs.topk.io"
},
{
"key": "security.encryption-at-rest",
"value": true,
"provenance": "company_stated",
"as_of": "2026-07-20",
"source_url": "docs.topk.io"
},
"…"
]
}
}MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company_facts({ domain: "topk.io", 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.