TikLet — an interactive control panel for TikTok Live streamers

TikTok Live Studio on its own puts almost nothing on screen: gifts don't become alerts, goals aren't displayed, there's no way to queue a track from a chat command, and messages have to be read by eye — the streamer ends up watching chat instead of the camera.

Off-the-shelf international alert services don't fit Kazakhstan: they have no support for Kaspi, the country's default payment method, and they run through a cloud server, so an outage on their end cuts the overlays off mid-broadcast.

Even what does exist is scattered — alerts in one service, music in another, analytics in a third, each with its own link, its own account and its own subscription.

We built a native Windows app that runs locally alongside TikTok Live Studio. More than ten widgets — like counter, viewers, gift alerts, chat, goals, hype train, giveaways, polls, top likers, PK battle score — are served from a local address and drop into Live Studio or OBS as an ordinary browser source, one link per widget. Setup comes down to typing a nickname: the app finds the live room itself and starts catching likes, gifts and chat.

The audience drives the interaction. The music bot builds a track queue from the !track chat command, and donors skip the line. Chat is read aloud with a profanity filter, with numbers and abbreviations spoken the way a person would say them, so the streamer stays on camera rather than in the message log. To hold viewers to the end there is Contexto, a mini-game where the whole chat guesses a word while progress and leaders show on screen.

Money and analytics are covered in the same place. TikLet reads Kaspi payment notifications on the same PC and turns them into an alert, a rising goal and a top-donor board with an automatic spoken thank-you — nothing to configure on the bank's side. After the stream, analytics break down viewers, likes, gifts, donations and retention in graphs. The licence is bound to the device and works offline: up to three devices per account, unbindable from the dashboard in one click, and the broadcast itself never depends on our server.