VelocityBot publishes what you scheduled, takes the payment in Stars, opens the private channel to whoever paid, and closes it again when their time runs out.
It is built for one person running several channels at once: every figure keeps its own bot, its own channels and its own voice, and they are all driven from one console.
Three jobs, all the ones nobody wants to do by hand at half past three in the morning.
A pass into the private channel, or a single post that unlocks once someone pays for it. Both go through Telegram Stars, so nobody has to leave the app and find a card.
Write the post, pick the time, close the laptop. The scheduler picks it up within a minute, and when Telegram has a bad minute it tries again instead of losing the post.
Access is dated. Once it lapses, the sweeper takes the person out of the channel — and lets them straight back in the moment they pay again.
A figure is a performer with everything that belongs to them: a bot, channels, a gallery, a voice. Nothing crosses between them, and switching figures takes one click in the console.
One container, two processes, one database. No queue, no cache, no second service to keep alive.
One application, three addresses. Each one serves what belongs to it and nothing else.
This page. Nothing here needs a login.
The console: posts, gallery, figures, people. Behind a login.
Where Telegram delivers updates. One address per bot, each with its own secret.