telegram-bot
Detecting the stack…
Python 3.12 · pip
DATABASE_URL
Waiting for deploy
Building
Operational
bot.my-project.com.ua
Connect the bot repository: the panel detects Python or Node.js, creates a database and starts the bot. After every push to GitHub it updates without downtime.
Control panel
Pick the bot repository, and the panel sets up the stack, the database, the launch and the webhook address by itself.
How a bot deploy goes in the panel: you pick a GitHub repository, the panel detects Python and creates a database by itself, starts the bot without downtime, sets up a webhook address with free SSL and sends a notification to Telegram.
Languages and libraries
The panel detects the language and dependencies of the bot by itself, and for everything else there is a Docker image.
The most popular language for bots
Bots in JavaScript and TypeScript
Fast bots with a small memory footprint
Bots in PHP and Laravel
A bot in any language from a ready image
Pay for the number of bots, not for megabytes: bots share the memory, CPU and disk of the tariff.
For a small bot
For one bot
For a few bots with a database
For a bot with an admin area and an API
For a studio or a network of bots
For big bots and networks
In every tariff
Paying for 3, 6 or 12 months is 5% cheaper.
Next to the bot you can run its API or admin area; they take a place just like a bot. App hosting
How it works
Sign in with GitHub and pick the bot repository, or upload a ZIP or give a Docker image.
Put the bot token into the environment variables; it does not belong in the code.
Python, Node.js, Go or PHP is detected automatically, and the database is created by itself.
After every push to GitHub the bot updates by itself, and every deploy sends a notification.
You write the bot; the panel takes care of running, restarts, updates and SSL
The bot does not depend on your computer: if the process crashes, the panel restarts it by itself.
After every push to GitHub the bot updates by itself without downtime, and a failed version rolls back to the last working one.
The bot token and API keys live in environment variables, not in the repository code.
The database the bot needs is created by itself, and the connection variables are written into the app.
For a webhook the bot gets an address with free SSL, without a server of your own or nginx setup.
A live bot log with search, a terminal and files in the browser: you see what the bot receives and where it fails.
Good to know
A bot needs a process that runs around the clock, a database for its users and an easy way to update the code. A home computer or free hosting falls asleep sooner or later, and your own VPS needs setting up.
A typical Telegram or Discord bot on Python or Node.js needs 128–256 MB of memory, so one bot is fine on the Mini or Hobby tariff. Several bots, or a bot with a database, an admin area and background tasks, are better on Starter or Startup.
If the bot serves thousands of users at once, processes media or calls neural networks, you can upgrade the tariff at any time without moving.
The bot updates after every push to GitHub: the panel builds the new version and swaps the old one without downtime. If the new version does not start, the bot goes back to the previous one, and users will not notice.
Pick a tariff and connect the repository, or write to us and we will help move your bot.