Over the past few months, we’ve been working on a project called PolyTalk.
The original goal was pretty simple: make real-time multilingual communication possible without depending on external translation APIs or cloud-only services.
While testing existing solutions, we noticed that many of them required sending conversations through third-party infrastructure. That works for some use cases, but it wasn’t a great fit for organizations that care about privacy, deployment flexibility, or keeping communication workflows under their own control.
So we started building a self-hosted, open-source speech-to-speech translation platform instead.
A few things we’ve focused on:
Real-time speech translation Self-hosted deployment Open-source core No external translation APIs Live audio translation
The project is still evolving, but it’s been interesting exploring the challenges of multilingual communication, local AI infrastructure, and real-time translation workflows.
I’d be curious to hear how others here approach translation.
Are you using cloud-based services, self-hosted tools, or something in between?
GitHub: https://github.com/PolyTalkIO/polytalk
Website: https://polytalk.io/
You must log in or register to comment.
It’s nice to you release as open source self hosted pj and also nice to see py and FastApi stack. There has multiple open source tts sst pipeline, what is your pj’s selling points? I can’t find in your src. Amd what exactly is near real-time? Sub 200 ms?
What We Learned Building a Self-Hosted Speech Translation Platform
Okay, but… what did you actually learn? Your post doesn’t go into it, and the links just go to the repository. (That’s a long README, by the way.) And a question lingers on my mind since it’s important to me personally: You use AI for the translating tech, of course, but how much AI is involved in the other parts of the project? (Such as code, documentation, testing, marketing posts like this one, …)
This is a pretty interesting project! Assuming one wanted to run everything locally, what’s the minimum viable hardware stack for near-realtime performance?
