TopK
Security Posture
Baseline security
As of September 24, 2026, TopK's security: SOC 2 Type I is confirmed, alongside encryption at rest, encryption in transit, and private networking. Type I covers design of controls, not operating effectiveness over time; buyers with Type II requirements will need to ask directly.
Backed by 5 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Every value derives from a dated, sourced capture — open any fact for its source.
Certifications
SOC 2 Type I
Controls
Encryption At RESTEncryption In TransitPrivate NetworkingRBAC
Security Change Historydated events · values unlock with a key
Security signal removed: Audit Logs · high significance
Security signal removed: SOC 2 · high significance
Security signal added: Private Networking · high significance
Security signal removed: VPC Peering · high significance
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
Every security fact on this pagekey · value · provenance · dated · sourced
| Fact | Value | Provenance | As of | Source |
|---|---|---|---|---|
| security.cert.soc2-type-i | SOC 2 Type I | company stated | 2026-09-24 | docs.topk.io |
| security.encryption-at-rest | Encryption At REST | company stated | 2026-09-24 | docs.topk.io |
| security.encryption-in-transit | Encryption In Transit | company stated | 2026-09-24 | docs.topk.io |
| security.private-networking | Private Networking | company stated | 2026-09-24 | docs.topk.io |
| security.rbac | RBAC | company stated | 2026-09-24 | docs.topk.io |
Security across Vector DatabasesTopK ranked in place · tap through for each read
| Company | Security read | Facts |
|---|---|---|
| Pinecone | Enterprise-grade | 14 |
| Zilliz | Compliance-ready | 14 |
| Turbopuffer | Compliance-ready | 12 |
| Qdrant | Compliance-ready | 11 |
| Weaviate | Compliance-ready | 10 |
| Chroma | Compliance-ready | 8 |
| TopK this record | Baseline security | 5 |
| Activeloop | Baseline security | 4 |
| Epsilla | Baseline security | 4 |
| Vectara | Compliance-ready | 3 |
No observed security facts yet for KDB.AI, LanceDB, Marqo, Milvus, MyScale and Vespa.
IdentityBixel ID · free forever
Operated by
No registered company joined yet. Would resolve with: a registry identifier for the entity; a legal page on the site naming the registered company.
Registry identifiers
None on record.
Published identifiers
- Crunchbase topk · inferred
- GitHub topk-io · inferred
- LinkedIn topkio · corroborated
- X topk_io · corroborated
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-type-i",
"value": true,
"provenance": "company_stated",
"as_of": "2026-09-24",
"source_url": "docs.topk.io"
},
{
"key": "security.encryption-at-rest",
"value": true,
"provenance": "company_stated",
"as_of": "2026-09-24",
"source_url": "docs.topk.io"
},
{
"key": "security.encryption-in-transit",
"value": true,
"provenance": "company_stated",
"as_of": "2026-09-24",
"source_url": "docs.topk.io"
},
{
"key": "security.private-networking",
"value": true,
"provenance": "company_stated",
"as_of": "2026-09-24",
"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.