This is an automated archive made by the Lemmit Bot.
The original was posted on /r/selfhosted by /u/Aggravating-Gap7783 on 2025-04-12 13:57:09+00:00.
Hi r/selfhosted, I'm Dmitry, founder of Vexa. Many of us are uncomfortable sending sensitive meeting recordings/transcripts to third-party cloud services like Otter.ai, Fireflies, Fathom, or using closed-source APIs like Recall.ai due to privacy, compliance, or data control concerns.
We're building Vexa as an open-source (Apache 2.0) infrastructure layer specifically to address this. It's designed from the ground up with self-hosting in mind, allowing you to keep all meeting data entirely within your own control.What's Vexa v0.2?We just launched v0.2, focusing on the core API functionality:
- Simple API: Programmatically send a bot to Google Meet.
- Real-Time Transcripts: Get live, multilingual transcripts streamed back via the API.
Self-Hosting & Current Status:While the easiest way to test the API functionality right now is via our free Cloud Beta, the entire stack is open source and designed for self-deployment. It uses a microservice architecture (details and deployment steps are in DEPLOYMENT.md in the GitHub repo).
You can run it yourself today if you're comfortable deploying containerized services.
- GitHub Repo (Code & Self-Hosting Docs):
We'd love feedback from the self-hosting community, especially on:
- Use cases where self-hosted transcription is critical.
- Thoughts on the microservice architecture for self-hosting.
- Challenges you've faced with cloud transcription tools.
Thanks for reading! I'll be around to answer questions.