Open-source meeting bots, real-time transcripts, and sandboxed AI agents.
Stream live transcripts from Google Meet, Teams, and Zoom into your own Markdown knowledge base.
Vexa sends automated bots into video calls to stream speaker-attributed transcripts and feed sandboxed AI agents. It suits engineering teams and technical professionals who want to own their meeting data without relying on third-party SaaS clouds.
The platform combines a meeting capture API for Google Meet, Microsoft Teams, Zoom, and Jitsi with an agentic runtime. Captured calls compile directly into a git repository of Markdown files, implementing an LLM Wiki pattern where agents maintain structured entity pages.
It suits developers and technical teams with Docker proficiency who want to self-host meeting intelligence or build custom transcription pipelines. It does not suit non-technical users looking for a simple web app that works out of the box without command-line configuration.
Spawns automated bots into Google Meet, Microsoft Teams, Zoom, and Jitsi calls.
Streams draft-then-confirmed, speaker-attributed transcripts in real time over WebSockets.
Automatically compiles meeting notes into a portable, grep-friendly Markdown knowledge base.
Executes coding agents in isolated Docker or Kubernetes containers with no unauthorized network egress.
Free under the Apache-2.0 licence when self-hosted, with an optional hosted SaaS at vexa.ai that provides $2 of free bot credit and charges approximately $0.30/hr thereafter.
880 open remote AI-training roles, updated November 15, 2026; most pay $20–$175 an hour. Zekai lists them free; the application goes to the employer’s platform.
These reviewed AI tools do the same job instantly — from our scored directory.
Vexa officially supports Google Meet, Microsoft Teams, Zoom, and has offline-proven support for Jitsi.
Yes, the transcription API is a complete standalone product where you send a bot and read the stream without running the agent lane.
When self-hosted, your transcripts compile into a local git repository of Markdown files on your own infrastructure.
See Zekai first in Google