For security and compliance
What you can verify,
and what isn’t built.
Written to be checked, not believed. It covers Vexa in your own infrastructure; each answer links to its code or docs.
vexa · inside your networkillustration
The callVexa, in your networkYour storageYour modelYour network
- The call
- Vexa, in your network
- Your storage
- Your model
- Your network
Where it runs and what flows
Comes in
- The callZoom, Microsoft Teams or Google Meet
Your network
- Vexa joins the callAs a participant, under the name you give it
- TranscriptionThe unit you run, or an OpenAI-compatible endpoint you host
- Object storageRecordings and the notes workspace
- PostgresMeetings and transcripts
- RedisLive transcripts, while a meeting runs
- AgentNotes and questions, from the record
- Your model endpointA model you host, or Anthropic with your firm’s own key
Leaves only where you point it
- Hosted transcriptionThe quickstart’s default, on Cloudflare Workers AI, until you point Vexa at your ownSub-processors
- Email and webhooksYour mail server, the addresses you configure
- AnthropicIf you point the agent there, with your firm’s key
- The internetThe agent’s web tools are on by default
stays inside your networkthe call, from outsideleaves only where you point it
Where your records land
On infrastructure you run.
- Notes workspace
- Markdown files in git, readable without Vexa
- Recording is on by default.
Which model reads them
Two models touch a meeting, and you choose both.
- Speech to text
- Your transcription unit, or an endpoint you host
- Notes and questions
- Vexa’s agent, on Anthropic’s Claude Code
- Its model
- Anthropic, or yours through an OpenAI-compatible gateway
What leaves your network
With transcription and your model inside your network, the audio path never calls out.
Leaves only where you point it
- The connection to the meeting, on Zoom, Teams or Meet
- Calls to the model endpoint you configure
- Email, through the mail server you configure
- Webhooks, to the addresses you configure
What you restrict yourself
- Shipped Compose and Helm defaults don’t firewall agent containers.
- The agent’s web tools are on by default.
- Its command-line tool keeps telemetry and update checks on.
- Apply your own network policy.
Checked, and not yet
- The architecture file checks the audio path in continuous integration.
- It does not yet cover model calls, email or webhooks.
- On Kubernetes one setting still goes through
extraEnv. - We have never run Vexa on a disconnected network.
Consent today
Vexa has no consent or notice feature.
Waiting in the lobbymock-upYour firmwants to join
- Teams and Meet hosts may have to admit it.
- With a calendar connected, it joins meetings as they start.
- Turn auto-join off per calendar or per meeting.
- Nothing asks before each meeting.
Not built yet
- A read audit log
- Retention controls Roadmap
- SAML or generic OIDC sign-in, and SCIM provisioning
- Encryption at restFor transcripts, notes and stored keys.
- Backup and restoreNothing in the release does it.
- CertificationsNo external audit or published penetration test.
Read the code
Vexa is open source under Apache-2.0. Your engineers can read every line.
Files a reviewer can check
architecture.calm.json- every service, data store and flow
SECURITY.md- how to report a vulnerability
security-insights.yml- the Security Insights manifest
license-exceptions.jsonandTHIRD_PARTY_LICENSES.md- every dependency’s licence, with each exception explained
- If the company went away, the code would stay yours.
- Its open core is approved by FINOS.
Where it runs
Transcription runs as its own unit. Vexa is a Red Hat Ready Partner.
Docker ComposeLite, one containerKubernetes, with HelmOpenShift, with Helm
Go deeper
- Security & compliance
- deployment posture, trust model, audit artifacts
- Architecture review
- where the audio goes, and what isn’t claimed
- Identity
- the access model, and what is wired today
- Kubernetes
- the Helm install, sign-in and no-egress clusters
- Status
- capability by capability
Hosted Vexa is a different deployment
The hosted service at vexa.ai runs in the United States, records by default, and doesn’t run the agent.
A question this page doesn’t answer?
Bring it to a call with the founder.