October Infrastructure Sale · code OCTOBER15 — until 1 Nov See the offer →
Telegram · Discord · Bots · Always on

A home for your bot that doesn’t sleep.

Free tiers sleep, dyno hours run out, laptops close. A $2.59 VPS runs the bot 24×7 — and 500 more like it.

Every bot developer follows the same arc: it starts on a free tier, the free tier sleeps or the hours run out, the bot goes quiet, users complain. The fix isn’t a bigger free tier — it’s a $2.59 VPS where the process just stays up.

One VPS doesn’t run "a bot" — it runs as many as you write. Python, Node, Go; long-polling or webhooks; a systemd unit each and they all share the box. Most bot devs never outgrow the smallest tier.

For bots serving Indian users, in-country hosting trims webhook and API-call latency — small per call, meaningful across thousands.

Set up in 5 steps.

  • 1. Deploy the smallest Linux VPS — Hut at $2.59/mo is genuinely enough for most bots.
  • 2. Install your runtime (python3-venv, Node via nvm, Go, whatever).
  • 3. Clone the bot, install deps, add a systemd unit so it restarts on crash and on boot.
  • 4. Webhooks? Put Caddy or nginx in front for TLS and point Telegram at your domain. Long-polling needs nothing extra.
  • 5. Ship it — then add the next bot to the same box.

Recommended tiers

Hut — $2.59/mo
1GB — several Python/Node bots + webhooks
Deploy →

Cabin — $3.79/mo
2GB — bots + a database + a dashboard alongside
Deploy →

Common mistakes

  • • Running the bot in a bare shell — one SSH disconnect kills it. systemd or a supervisor is five minutes of setup.
  • • Putting the token in the repo — use env vars or a .env file excluded from git.
  • • Paying per-dyno or per-execution pricing — a flat VPS hosts unlimited bots for one price.
  • • No logging — journald captures stdout free; wire it up before you need it.

When this is NOT enough

You’ll know: thousands of concurrent webhook hits, heavy image/video processing per message, or a database that’s outgrown shared RAM. That’s the 4–8GB tiers — still in place, same IP. If one bot gets truly huge it probably deserves its own box anyway.

Real questions

Bot hosting FAQ

Runtimes, webhooks and how many bots fit.

Ask on Discord ↗
Dozens of typical Python/Node bots — they’re tiny. RAM and CPU become the limit only at serious webhook volume.
Long-polling is simplest and works on any outbound connection. Webhooks scale better and need a domain + TLS — Caddy makes that a two-line config.
Anything — it’s a full Linux root server. python-telegram-bot, Telegraf, discord.py, grammY, your own stack.
Yes — it runs under systemd on the server. Your laptop is irrelevant to it.
Free tiers sleep, cap hours, or throttle. This is a dedicated slice that stays up — and the 7-day refund makes trying it risk-free.
Telegram’s DCs are global so latency is a wash — the India benefit is when your bot calls Indian APIs or serves Indian users’ data.