Put a room recording through the same pipeline your online meetings already use.
What it does
- Takes an audio file from a meeting that happened in a room — no bot, no call.
- Runs it through the same transcription path as a live meeting.
- Returns a transcript addressable by the same API and the same meeting record.
- Runs on your own infrastructure; the audio never leaves it.
What exists today
Vexa captures meetings a bot joins — Google Meet, Zoom and Microsoft Teams. A meeting that happened in a room, with nobody dialled in, has no route in today.What this adds
An upload route into the existing pipeline, so in-person meetings land in the same place as online ones.How sponsorship works
You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so “done” means done on your meetings. Your name goes on the release note. Sponsorship buys the order of the queue — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.Two doors
Sponsor this
Fifteen minutes. Bring the constraint you are under.
Watch this
One email when it ships. The mail is already written — send it as it is.
Questions
Can Vexa transcribe a recording of an in-person meeting?
Can Vexa transcribe a recording of an in-person meeting?
No. Vexa captures meetings a bot joins — Google Meet, Zoom and Microsoft Teams. A meeting held in a room, with nobody dialled in, has no route in.
What would sponsoring this add?
What would sponsoring this add?
An upload route into the existing pipeline, so in-person meetings land in the same place as online ones.
Where does it run?
Where does it run?
On your own infrastructure. Vexa is Apache-2.0 and self-hosted — the audio and the transcript stay inside it.
Ships upstream Apache-2.0 when sponsored.