# Vexa

> Vexa is open-source AI that turns your company's meetings into knowledge it owns, on your own servers, with your own model. It starts with your Zoom, Microsoft Teams and Google Meet calls. The code is open source under Apache-2.0, with an open core approved by FINOS.

Vexa joins Google Meet, Microsoft Teams and Zoom calls as a participant, records them, and returns the transcript while the meeting is still running. A company can run it on its own servers, or use the hosted service at vexa.ai. Because the code is Apache-2.0, it stays with the company if the vendor goes.

## Facts

- Licence: Apache-2.0. Source code: https://github.com/Vexa-ai/vexa
- Where it runs: hosted at vexa.ai, or self-hosted with Docker Compose, as a single container (Vexa Lite), or on Kubernetes with Helm.
- Models: transcription and the language model can both be ones the company runs itself.
- What runs today: meeting capture (recording and transcript) for Google Meet, Microsoft Teams and Zoom. In a self-hosted Vexa, a workspace and agents also run, in early form.
- Not captured: phone calls, Webex and in-person meetings.
- Not built yet: a read audit log, retention controls, SSO/SAML. The roadmap lists every planned item: https://vexa.ai/roadmap
- Governance: open core approved by FINOS, the Fintech Open Source Foundation (https://github.com/finos/technical-oversight-committee/pull/298).
- Partner programme: Red Hat Ready Partner.
- Company: Vexa.ai Inc. Founder: Dmitry Grankin (https://www.linkedin.com/in/dmitry-grankin/).

## For firms in finance

- [Vexa for finance](https://vexa.ai/finance): your firm's meetings, recorded and transcribed on your own servers
- [Distribution and investor relations](https://vexa.ai/finance/distribution): every advisor and investor call, recorded on your own servers
- [Credit and diligence](https://vexa.ai/finance/credit): a diligence record your firm owns
- [Security review](https://vexa.ai/security): what a security team can verify in a self-hosted Vexa, and what is not built
- [Book a demo](https://vexa.ai/contact)

## Product

- [Meeting capture](https://vexa.ai/product/capture): Zoom, Teams and Google Meet calls, recorded and transcribed
- [Workspace](https://vexa.ai/product/workspace): meetings as Markdown files on your own servers (self-hosted, early)
- [Agents](https://vexa.ai/product/agents): write-ups and answers from your meetings, with your own model (self-hosted, early)
- [Self-host Vexa](https://vexa.ai/self-host): Docker Compose, one container, or Kubernetes
- [Pricing](https://vexa.ai/pricing)
- [Roadmap](https://vexa.ai/roadmap): what is planned and not built yet

## For developers

- [Documentation](https://docs.vexa.ai): the docs keep their own index at https://docs.vexa.ai/llms.txt and every page flattened at https://docs.vexa.ai/llms-full.txt
- [Quickstart](https://docs.vexa.ai/quickstart): hosted in one API call, or self-hosted
- [Connect your agent](https://vexa.ai/connect): Claude Code or Codex reach your meetings through the Vexa MCP server
- [Google Meet transcription API](https://vexa.ai/product/google-meet-transcription-api)
- [Microsoft Teams transcription API](https://vexa.ai/product/microsoft-teams-transcription-api)
- [Zoom transcription API](https://vexa.ai/product/zoom-transcription-api)
- [Claude and MCP](https://vexa.ai/integrations/claude-mcp)
- [n8n](https://vexa.ai/integrations/n8n)
- [Webhooks](https://vexa.ai/integrations/webhooks): what Vexa sends when a meeting ends; there is no CRM connector
- [Vexa vs Recall.ai](https://vexa.ai/compare/recall-ai)

## Optional

- [Blog](https://vexa.ai/blog)
- [GitHub organisation](https://github.com/Vexa-ai)
- [LinkedIn](https://www.linkedin.com/company/vexa-ai/)