> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vexa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Upload a recording of an in-person meeting

> Put a recording of an in-person meeting through the same Vexa transcription pipeline your online meetings already use — self-hosted, nothing leaves your infrastructure.

**Can Vexa transcribe a recording of an in-person meeting?**

**Today:** 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.

**Sponsorable:** yes — An upload route into the existing pipeline, so in-person meetings land in the same place as online ones.

***

*Put a room recording through the same pipeline your online meetings already use.*

|                 |                                    |
| --------------- | ---------------------------------- |
| **Status**      | **sponsorable**                    |
| **Size**        | size pending                       |
| **North star**  | 1 · Capture anywhere, owned by you |
| **Measured by** | platforms and routes covered       |

## 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

<Columns cols={2}>
  <Card title="Sponsor this" icon="handshake" color="#0D9373" href="https://cal.com/dmitrygrankin/web?utm_source=docs&utm_medium=roadmap&utm_campaign=sponsor&utm_content=in-person-upload" horizontal arrow cta="Book fifteen minutes">
    Fifteen minutes. Bring the constraint you are under.
  </Card>

  <Card title="Watch this" icon="envelope" color="#0D9373" href="mailto:dmitry@vexa.ai?subject=Roadmap%20update%3A%20Upload%20a%20recording%20of%20an%20in-person%20meeting&body=watch" horizontal arrow cta="Email me">
    One email when it ships. The mail is already written — send it as it is.
  </Card>
</Columns>

## Questions

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="What would sponsoring this add?">
    An upload route into the existing pipeline, so in-person meetings land in the same place as online ones.
  </Accordion>

  <Accordion title="Where does it run?">
    On your own infrastructure. Vexa is Apache-2.0 and self-hosted — the audio and the transcript stay inside it.
  </Accordion>
</AccordionGroup>

***

*Ships upstream Apache-2.0 when sponsored.*