Music in voice chats, without the dropouts.

We build and run Telegram music bots that stream into voice chats from a fleet of Go playback servers, with queues, seeking and failover that survives a data centre dropping the call.

Talk to an engineer →See everything we run

500K+active users

81,300groups protected

9,703apps deployed

50bare-metal machines

A playback fleet, not a single script

Our music platform runs on eleven Go playback servers behind one bot. Each chat stays on its server for the length of a session, and new chats go to the least-loaded server among the healthy ones only.

Health comes before load: a broken server can never look idle and quietly swallow new chats, which is the most common way music bots fail at scale.

Every track verified before it plays

A song that cuts off halfway is worse than a song that fails. Every download is checked against the real length of the track, and if the first source delivers a partial file, a second source is tried before anything reaches the voice chat.

What your music bot gets

Queues, playlists, seeking, skip and loop.
Voice-chat transport over WebRTC with jitter buffering.
Automatic failover when a data centre drops the call.
Idle detection, so assistants leave empty chats on their own.
Rolling updates that never stop playback for everyone at once.

Related systems

Running in production.

02 / 12

Voice Platforms

High-fidelity audio streaming injected seamlessly into Telegram voice chats. We engineered custom queueing, precise seeking, multi-chat playback synchronization, and aggressive reconnection protocols when a data centre unpredictably drops the call mid-track.

WebRTCOpusvoice node

05 / 12

Deploy Automation

Ship updates, instantly roll back, and know within seconds whether the new binary is serving traffic. Our deep health checks exercise real workloads against the database, because merely opening a listening port proves absolutely nothing.

Dockerhealth checkswatchdog

07 / 12

Observability Dashboards

The uncompromising operator view: instantly see what is currently running, what explicitly failed, what config changed, and what it cost on AWS. Built specifically for the tired engineer on call, not for a pretty marketing screenshot.

WorkersMongoDBtime series

Questions

Asked and answered.

Can you build a music bot like the popular ones?

Yes, and usually a more reliable one. We have run into and fixed the failure modes behind most of the dropouts people complain about.

How many groups can one music bot serve?

It scales horizontally: capacity grows by adding playback servers, and routing spreads chats across them automatically.

Do you host the music bot?

Yes. We run the playback fleet, watch it, and fix it when something breaks.

Telegram bot development Anti-spam bots AI agents Hosting & infrastructure Mini Apps Payment bots Scraping & automation Case study: Python to Go

07 Contact · no form, no email

The whole business runs on Telegram.

Message us and a person who works on the code answers. Say what is broken or what you want built — we will tell you plainly whether we are the right people for it.

Message @kustbhai →

updates↗

@kustbots

The official ledger of what we shipped, what changed, and what broke. Highly curated, low volume. Subscribe to stay in the loop without the noise.

community↗

@kustbotschat

Technical questions asked in the open, answered directly by our engineers where everyone else can read and learn from them.

support↗

@kustbhai

The direct batphone. Broken things, urgent requests, and new architectural work start right here. No chatbots, just us.