Vectara

Vectara, Inc.·Vectara.com
Security Posture

Compliance-ready

As of September 3, 2026, Vectara's security: SOC 2 Type II and HIPAA certifications are stated, and VPC Peering is listed as a control. Regulated-industry buyers clear the baseline compliance check; buyers needing FedRAMP or ISO 27001 will need to ask directly.

Backed by 3 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Certifications
SOC 2 Type IIHIPAA
Controls
VPC Peering
Security Change Historydated events · values unlock with a key
Security signal removed: Audit Logs · high significance
Security signal removed: CSA STAR · high significance
Security signal removed: FedRAMP · high significance
Security signal removed: ISO 27001 · high significance
Security signal removed: ISO 27017 · high significance
Security signal removed: PCI DSS · high significance
Security signal removed: Data Residency · high significance
Security signal removed: Private Networking · high significance
Every security fact on this pagekey · value · provenance · dated · sourced
FactValueProvenanceAs ofSource
security.cert.hipaaHIPAAcompany stated2026-09-03www.vectara.com/legal/security-at-vectara
security.cert.soc2-type-iiSOC 2 Type IIcompany stated2026-09-03www.vectara.com/legal/security-at-vectara
security.vpc-peeringVPC Peeringcompany stated2026-09-03www.vectara.com/business/platform
Security across Vector DatabasesVectara ranked in place · tap through for each read

No observed security facts yet for KDB.AI, LanceDB, Marqo, Milvus, MyScale and Vespa.

Get security for vectara.com via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/vectara.com/facts?dimension=security

{
  "data": {
    "facts": [
      {
        "key": "security.cert.hipaa",
        "value": true,
        "provenance": "company_stated",
        "as_of": "2026-09-03",
        "source_url": "www.vectara.com/legal/security-at-vectara"
      },
      {
        "key": "security.cert.soc2-type-ii",
        "value": true,
        "provenance": "company_stated",
        "as_of": "2026-09-03",
        "source_url": "www.vectara.com/legal/security-at-vectara"
      },
      {
        "key": "security.vpc-peering",
        "value": true,
        "provenance": "company_stated",
        "as_of": "2026-09-03",
        "source_url": "www.vectara.com/business/platform"
      },
      "…"
    ]
  }
}
MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company_facts({ domain: "vectara.com", dimension: "security" })

# returns the security record above,
# each value with its source_url + as_of,
# ready to reason over
Build 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.