Frogus CloudVPS for Telegram bots
On a server your bot runs around the clock, does not depend on your computer and restarts by itself after a failure. The server is in the Netherlands.
How much a bot needs
| Bot | Cores | Memory | Disk | Plan |
|---|---|---|---|---|
| Simple Python (aiogram) or Node.js (grammY, Telegraf) bot without a database | 1 | 1 GB | 10 GB | VPS-1 |
| Bot with PostgreSQL or Redis, several bots on one server | 1–2 | 2 GB | 20–30 GB | VPS-2 |
| Bot with a task queue, web panel or file processing | 2 | 4 GB | 40 GB | VPS-3 |
The bot itself usually takes tens of megabytes; the rest is for the system, the database and headroom for spikes. You can also build your own configuration in the configurator — exactly the cores and memory you need.
Matching plans
Add resources at any time from the client area.
Questions
Is 1 GB of memory enough for a bot?
For one bot without a database, yes. If PostgreSQL or several bots run alongside, take 2 GB.
Webhook or long polling?
Both work. Long polling only needs outbound internet access; a webhook needs a domain with HTTPS.
Is traffic limited?
Volume is unlimited: the first 5 TB a month at full speed, then 100 Mbit/s — far more than any bot needs.
Step-by-step guides (in Russian): running a bot with systemd, first server setup.