How it works
Your bot goes through several automatic steps before it answers its first message.
Steps
Upload the source
You upload a ZIP archive or connect a GitHub repository. Any .env file is stripped automatically so tokens never leak into the archive.
Detect language and standards
The system detects Python, Node.js or Go, then checks 6 standard rules: the token is read from BOT_TOKEN, Telegram API access (automatic — requests are routed through the platform proxy whatever the bot uses, nothing to configure), library versions are pinned, there is a clear entry point, all persistent data is written under DATA_DIR, and .env.example documents every setting.
Security scan
The code also runs through a security scanner — suspicious calls, exposed tokens and similar issues are flagged with a traffic light: 🟢 no issues, 🟡 warning, 🔴 build stops.
Build
A Docker image is built for the code.
Smoke test
The bot runs in a throwaway container for 30 seconds — calls, errors and crashes are monitored. If the test fails, the bot is not started and the reason is shown.
Review
The first bot on a new account may go through an extra manual review step, as an anti-abuse measure. Later bots usually pass through immediately.
Free trial
The bot runs free for 3 days, so you can try it with real users.
Payment
After the trial, you pick a plan and pay via a card-to-card bank transfer. A staff member usually confirms it within ~30 minutes, after which the bot runs continuously. Pricing: Pricing.
Running
The bot runs continuously. Unless "always on" is enabled, a bot stays running while the server has free memory; when resources run low, an idle bot may be put to sleep and wakes within a few seconds on the next message. An automatic backup runs every day at 03:00 Tashkent time.