vexa
Vexa sends a bot into Google Meet, Microsoft Teams and Zoom calls and streams speaker-attributed transcripts in real time, through its hosted API or a stack you run yourself. The README says Jitsi join and capture are proven offline but live validation is still pending. On top of the transcripts, self-hosted installs add sandboxed agents that compile meetings into a Markdown knowledge base in a git repository you own; the README states the sandboxed knowledge agents are self-hosted only. If you only need transcription, the README says you can ignore the agent side entirely.
To try it hosted, sign in at vexa.ai and POST to `/bots` with a platform (`google_meet`, `teams`, `zoom` or `jitsi`) and the meeting code, then read `/transcripts/...`; new accounts get $5 of free bot credit with no card, according to the README. To self-host, `make all` pulls the published Docker images and starts the full Compose stack, printing an API key and URLs for a web workbench and the API gateway; `make lite` is a lighter single-container image. It needs Docker 26 or newer and a speech-to-text source (a free token or your own GPU transcription unit), and building from source wants 8 vCPUs and 16 GB RAM. Bots and agents each run in isolated, ephemeral containers. It is Apache-2.0 licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-09
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 11
- Latest release
- v0.12.28 (2026-10-09)
- Open issues
- 700
- Recent issues with at least one comment
- 0/6
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #938 [PLATFORM] Zoom unsigned guest joins depend on browser generation; stock Chromium 141 is policy-blocked37 comments · 2026-07-23
- #956 mixed attribution: trailing platform identity names a new acoustic turn before causal evidence exists28 comments · 2026-07-24
- #841 webhooks: deliveries reach the receiver but the dashboard's Delivery History never shows them — users read a store nothing writes22 comments · 2026-07-19
- #797 speaker hints (Teams+Zoom): name resolution misses on live DOM and the no-name guard discards every detection SILENTLY — signal detection it21 comments · 2026-07-18
- #839 gmeet: a bot stopped while in the waiting lobby is destroyed but never visibly leaves — the knock is abandoned, not withdrawn17 comments · 2026-07-19
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!