Telegram bot hosting that stays up 24/7
A Telegram bot has to be running to answer anyone. Put it on a panel and it runs day and night in its own container, restarts itself if it crashes, and keeps the logs so you can see what happened.
Four steps to a bot that answers
- Create a worker panel. Worker is the type for anything with no public web page. Your bot talks out to Telegram, so it does not need a URL of its own.
- Add your files. Upload them, edit them in the browser, or let your AI write them. Dependencies install from package.json or requirements.txt when the panel starts.
- Put the token in an environment variable. Save BOT_TOKEN on the panel rather than in the code. It is encrypted at rest and cannot be read back out.
- Press start. Watch the live log stream to see it connect. From then on it stays running until you stop it or the panel expires.
The things that usually kill a hobby bot
- No idle sleep. A worker panel runs whether anyone messaged it or not.
- Restarted on failure up to five times, so a dropped connection recovers itself.
- Logs kept after the process exits, with the exit code, so a crash is diagnosable.
- The restart count is visible, which is how you spot a crash loop.
- Its own RAM and CPU limit, so a runaway loop cannot take the machine with it.
- Files stay put when the panel is stopped, and through a renewal.
Polling or webhook, both work
Long polling needs nothing public. Run it as a worker and you are done, which is why most bots on Redon3 are set up that way.
If you would rather use a webhook, set the panel type to web instead, tell it the port your server listens on, and reserve a name like yourbot.redon3.com. That comes with the HTTPS Telegram requires, and then you call setWebhook with that URL.
Or let your AI run it
Add Redon3 as a connector in ChatGPT or Claude and your assistant can write the bot, set the runtime and start file, store the token, start the panel, and read the logs when something breaks. It cannot delete the panel and it cannot spend money.
That matters most for the boring failure a week later. Instead of pulling the logs yourself, you say the bot stopped and your assistant goes and looks.
Common questions
- Can I host a Telegram bot 24/7?
- Yes. A worker panel runs continuously and is restarted on failure. There is no idle timeout and no sleeping, so the bot answers at three in the morning as well as at noon.
- Which plan do I need for a Telegram bot?
- Starter at 4.99 USD per 30 days covers most bots: 450 MB RAM, half a CPU, 1 GB of storage. Builder gives you 1 GB of RAM if you are caching data or running something heavier.
- Do I need a public URL or a webhook?
- Not for long polling, which is the simplest setup and needs nothing public. If you want a webhook, run the panel as a web app and reserve a subdomain, which comes with the HTTPS Telegram requires.
- Where do I put my bot token?
- In an environment variable on the panel. It is encrypted at rest, and nothing can read the value back once it is saved, so it never sits in your code or in a chat log.
- Can I run more than one bot?
- Yes. Either one panel per bot, billed separately, or one process that handles several bots if you would rather keep them together.
- Is there a free trial?
- New accounts get a free trial panel for seven days with no card, which is enough to get a bot connected and watch it run before you pay for anything.