Telegram Bot Hosting

Paste the token from @BotFather on the Bot page. The panel checks it with Telegram before your bot starts, then shows the bot's @username and a link to open it in Telegram. The token is stored encrypted and handed to your code as BOT_TOKEN and TELEGRAM_BOT_TOKEN, so most examples run without changes.

Some libraries hide a dead bot. aiogram and pyTelegramBotAPI keep retrying when the token is wrong or when the same bot runs somewhere else, so the process stays up and nothing answers. The panel reads the console and says which one it is: "Telegram did not accept the token", or "Another copy of this bot is running", which is Telegram's 409 Conflict error.

We measured each library with a bot built and ready to start, on our own servers:

The 0.5 GB STARTER plan runs any of them with room for your own code. Choose 1 GB or more when the bot keeps data in memory, handles files or images, or runs several bots in one process.

Your bot works with long polling out of the box: it asks Telegram for new messages and needs no address of its own. A webhook needs a public HTTPS address, which these plans do not include yet. If your code sets a webhook, the panel shows it and offers to remove it, so polling works again without losing waiting messages.

Upload your files over SFTP or from a Git repository, add packages to requirements.txt or package.json, and press Start. Stop the old copy first: Telegram lets only one copy of a bot read messages, and the panel will tell you if another one is still running.