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

# Bots on Google Meet, Zoom and Microsoft Teams

> A Vexa bot joins your Google Meet, Zoom or Microsoft Teams call and returns the transcript live over the API — Apache-2.0, self-hosted with no egress.

**Can Vexa send a bot to a Google Meet, Zoom or Microsoft Teams meeting?**

**Today:** Yes. A bot joins with one API call and the transcript arrives live, self-hosted on your own infrastructure.

**Sponsorable:** no — this one is shipped.

***

*A bot joins the call and you get the transcript live over the API.*

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

## What it does

* Send a bot to a meeting with one API call.
* Transcript segments arrive while the meeting is still running.
* Runs self-hosted on your own infrastructure.

This one is shipped — there is nothing to sponsor. See the [roadmap](/roadmap) for what is not.

## Questions

<AccordionGroup>
  <Accordion title="Can Vexa send a bot to a Google Meet, Zoom or Microsoft Teams meeting?">
    Yes. A bot joins with one API call and the transcript arrives live, self-hosted on your own infrastructure.
  </Accordion>

  <Accordion title="Do I have to pay for this?">
    No. It is shipped and open source under Apache-2.0. Run it yourself, or use the hosted service.
  </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>

***

*Shipped upstream under Apache-2.0.*