Telegram bot hosting in 2026: the options compared
A Telegram bot needs a process that never stops, or a public HTTPS address for a webhook. On Livops it runs from a GitHub push for 19 credits a month (19,000 so'm). Here is how a VPS, Railway, Render, Fly.io and Vercel compare.
By Livops team, the people who build and run LivopsUpdated
A Telegram bot is a program that has to be running whenever somebody writes to it. Anywhere that keeps a process up will host one; the differences are what a month costs, how you pay, where the server is, and how much of the machine is left for you to look after. This page compares the usual choices with each provider’s own numbers, and ends with how it runs on Livops.
What does a Telegram bot need in production?
A process that stays up, or an HTTPS address
Telegram delivers updates in one of two ways, and a bot uses one or the other, never both[1]. With polling (getUpdates) the bot asks Telegram for new messages in a loop, so the process must never stop — anything that puts idle processes to sleep stops the bot. With a webhook Telegram sends each update to an HTTPS address, on port 443, 80, 88 or 8443[1], so you need a public address with a certificate, but the code only has to answer requests.
The token kept out of the code
The token BotFather gives you is the bot. It belongs in an environment variable, not in the repository.
Somewhere to keep data
A bot that remembers its users needs a disk that survives a restart, or a database.
Somebody to restart it
A bot crashes on an unexpected message sooner or later. Something has to start it again and tell you why it stopped.
The options at a glance
| Option | What it is | Smallest paid always-on process | What you still maintain |
|---|---|---|---|
| Livops | A platform; servers in Uzbekistan | 19 credits (19,000 so’m) a month | Your code |
| A VPS in Uzbekistan | A virtual machine with root | 82,000 so’m a month: 1 vCPU, 2 GB, 30 GB HDD (SmartCloud)[2] | The system, updates, a process manager, deploys, HTTPS for a webhook |
| Railway | A platform billed by usage | Hobby plan: $5 a month, including the same amount of usage[3] | Your code |
| Render | A platform with background workers | $7 a month: 0.5 CPU, 512 MB[5] | Your code |
| Fly.io | Virtual machines billed by the second | $2.19 a month: shared-cpu-1x, 256 MB[9] | Your code |
| Vercel | Functions; always-on Daemons in beta | Daemon pricing is not stated[11] | Your code |
Other providers’ prices are from each provider’s own page, read on 19 November 2026; the dates are in Sources below. Livops prices are the ones the cabinet bills today.
Each option
Livops
A bot is its own service type: always running, with no public address needed. Connect a GitHub repository or upload a folder, put the token in Variables, and every git push ships a new version. Payment is in so’m through Payme or Click, Uzbekistan’s payment services, and the servers are in Uzbekistan — close to users there, farther from users elsewhere. You do not get root on the machine; if you need to install system software of your own, a VPS is the better fit.
A VPS
The most control for the money: root, any software, any number of bots on one machine. The cheapest 2 GB machine at SmartCloud is 82,000 so’m a month[2]. In exchange, everything between the machine and a running bot is yours: the operating system and its updates, a service that restarts the bot, the deploy, and a certificate if you use a webhook.
Railway
The Hobby plan is $5 a month and includes that much usage[3]. It is paid by credit card[3]. Hobby services run always-on[3]. Its regions are in California, Virginia, Amsterdam and Singapore[4] — closer than Uzbekistan to users in those places.
Render
A background worker is a service that runs continuously and receives no incoming traffic[7] — a polling bot fits it exactly. The smallest paid size is $7 a month for 0.5 CPU and 512 MB[5]. Regions are Oregon, Ohio, Virginia, Frankfurt and Singapore[8].
Fly.io
The smallest machine, shared-cpu-1x with 256 MB, is $2.19 a month, billed by the second while it runs[9] — the lowest dollar price in this table. A credit card on file is required, and a stopped machine still pays for its root file system[9].
Vercel
Vercel Functions answer requests, and on the free Hobby plan each call may run for at most 300 seconds[10]: enough for a webhook handler, not for a polling loop. For a process that keeps running, Vercel has Daemons, in beta: it keeps the number of instances you configure running and restarts any that exit, but during the beta they accept no inbound HTTP or TCP traffic[11]. Pro is $20 a month[12].
VPS or platform: what do you maintain?
On a VPS you are the operations team: when the disk fills or a security update lands, it is yours to notice. On a platform — Livops, Railway, Render, Fly.io — you hand over code and the platform runs it; you give up root in return. If you enjoy running servers, a VPS gives you the whole machine. If you would rather spend the time on the bot, use a platform.
Where can you run a bot for free?
- Livops has no free tier for bots. On an account that has not paid yet, the first bot or app runs for 15 minutes on a zero balance, once, so you can watch it answer; static sites are free.
- Render gives free instances to web services, Postgres, Key Value and static sites, not to background workers; a free web service spins down after 15 minutes without inbound traffic and takes about a minute to start again[6].
- Railway has a Free plan with $1 of usage a month, up to 1 vCPU and 0.5 GB per service, and its services sleep after 5 to 10 minutes without outbound traffic; a trial gives $5 of credit for 30 days with no card[3].
- Fly.io has no free tier for new organizations; a trial gives $1 of credit for 7 days[9].
- Vercel Hobby is free[12], with the 300-second limit per function call above[10].
Telegram bot hosting on Livops
- In the cabinet, create a project and choose the source: a GitHub repository, an uploaded folder or
.zip, or the aiogram 3 bot + Redis template. - Paste the token BotFather gave you into the Bot token field, or add it under Variables with the name your code reads (often
BOT_TOKEN). Mark a variable as secret and its value is never shown again. - Deploy. The log shows the build, and the bot answers in Telegram once it starts. If the build fails, the previous version keeps running. A bot’s previous version is stopped before the new one starts, because two copies polling Telegram would conflict, so a bot that fails to start stays down until a deploy succeeds.
You can also send @livops_bot the name of a repository: the project is created and starts building without opening the cabinet.
The type and the start command are detected. A Python bot is found by its file — bot.py, main.py, app.py, run.py, or a file with if __name__ == "__main__". To set them yourself, put livops.json in the repository root:
{
"kind": "bot",
"start": ".venv/bin/python bot.py"
}
Polling is the default. To use a webhook, switch the bot’s Connection to Telegram in the project and press Save and redeploy; the bot is rebuilt in the new mode and the platform tells Telegram the address, using the token in BOT_TOKEN. Your code listens on PORT, receives on WEBHOOK_PATH, checks WEBHOOK_SECRET, and does not call setWebhook itself.
- If the process exits, it is started again. If it keeps crashing, it is stopped, and you are told with the last line it printed — in the cabinet, and in Telegram if your account is linked.
- Files written to
/app/data(theDATA_DIRvariable) are kept across restarts and deploys;/tmpis wiped. - The clock runs on UTC. For schedules in Tashkent time, add
TZ=Asia/Tashkentunder Variables and deploy again.
A bot is 19 credits a month (19,000 so’m). One credit is 1,000 so’m, and bought credits never expire. See Pricing for plans, which give more credits than they cost.
Questions
Which libraries work on Livops?
On Node.js: Telegraf, grammY and plain Node. On Python: aiogram, pyTelegramBotAPI and python-telegram-bot. A bot in another language runs from its own Dockerfile.
Polling or webhook?
Both. Polling is the default and needs nothing set up. With a webhook, the platform gives Telegram the address itself, using the token in BOT_TOKEN: your code listens on PORT, receives on WEBHOOK_PATH and checks WEBHOOK_SECRET, and never calls setWebhook.
What happens if my bot crashes?
It is started again on its own, and the project page counts the restarts. If it keeps falling over, it is stopped, and you are told with the last line it printed: in the cabinet, and in Telegram if your account is linked to the Livops bot.
Where does the bot keep its data?
In /app/data, whose path is also in the DATA_DIR variable. It survives restarts and deploys; /tmp and the code folder do not. For orders or payments, use a PostgreSQL database, which is backed up.
How much does a bot cost on Livops?
19 credits a month, which is 19,000 so'm at 1,000 so'm a credit. There is no free trial, but on an account that has not paid yet the first bot or app runs for 15 minutes on a zero balance, once, so you can see it answer.
Do I need a card?
No. Credits are bought in so'm through Payme or Click, Uzbekistan's payment services, and no card has to be linked.
Who wrote this comparison?
The Livops team. Every price and limit of another provider on this page links to that provider's own page, with the day we read it.
Sources
- Telegram Bot API — Getting updates (core.telegram.org). Checked .
- SmartCloud — VDS plans (smartcloud.uz). Checked .
- Railway — Pricing (railway.com). Checked .
- Railway — Deployment regions (docs.railway.com). Checked .
- Render — Pricing (render.com). Checked .
- Render — Deploy for free (render.com). Checked .
- Render — Background workers (render.com). Checked .
- Render — Regions (render.com). Checked .
- Fly.io — Pricing (docs.fly.io). Checked .
- Vercel — Functions limits (vercel.com). Checked .
- Vercel — Running Docker on Vercel (vercel.com). Checked .
- Vercel — Pricing (vercel.com). Checked .
Put your project online today
Connect GitHub or drop a folder. No card is asked for.
Start with your bot