Choosing a Telegram Bot Plan: Free, Starter, Pro or Ultra
Which Kerit Cloud Telegram plan fits your bot — what Free, Starter, Pro and Ultra include, typical workloads for each, and the signals that it's time to upgrade.
On this page
Every Kerit Cloud Telegram plan runs your bot as a persistent process on AMD EPYC hardware with NVMe storage, zero sleep mode, automatic restarts and under 40 ms latency to the Telegram API from the Virginia edge. Long polling and webhooks both work on every tier, and session files survive restarts and redeploys. The plans differ in resources, databases, backups and a few features for larger deployments.
The plans at a glance
| Free | Starter | Pro | Ultra | |
|---|---|---|---|---|
| Price | ₹0 forever | ₹99/mo | ₹199/mo | ₹399/mo |
| RAM | 256 MB | 1 GB | 2 GB | 4 GB |
| CPU (AMD EPYC) | 30% | 100% | 200% | 400% |
| NVMe storage | 2 GB | 5 GB | 10 GB | 20 GB |
| Databases | Shared MySQL | MySQL | MySQL + PostgreSQL | MySQL + PostgreSQL + Redis |
| Git deploy | — | Yes | Yes | Yes |
| Backups | — | Daily | Daily + 1-click restore | Daily + 1-click restore |
| Multiple bots per server | — | — | — | Yes |
| Region choice | — | — | — | Yes |
| Support | Standard | Standard | Priority | 24/7 priority |
| Uptime target | 99.9% | 99.9% | 99.9% | 99.99% |
CPU percentages are shares of a core: 100% is a full core, 400% is four. Paid plans come with a 3-day money-back guarantee and accept UPI, PayPal, crypto and cards.
Free — real hardware at zero cost
The free plan is not a trial. It runs your bot forever with no card required, on the same EPYC hardware as paid plans. 256 MB of RAM is more than it sounds for Telegram: a typical aiogram bot on long polling idles around 70 MB.
Good for: personal bots, small community bots, learning, and testing a bot before launch.
Limits to know: a shared MySQL database, no backups and no git deploy — you upload files through the panel or SFTP. The free tier is best-effort and excluded from SLA credits, so move to a paid plan once people depend on the bot. More in free hosting for Telegram bots.
Starter — for growing bots
Four times the memory, a full core, 5 GB of storage, your own MySQL database, git deploy and daily backups.
Good for: bots with a real user base and a database — reminder bots, group helpers, small shop bots. Git deploy alone is worth the upgrade for anyone updating their bot often: push to your repository and the bot redeploys.
Pro — the best value for most serious bots
2 GB of RAM, two cores, 10 GB of storage, PostgreSQL alongside MySQL, one-click restore and priority support. It’s marked “Most Popular” for good reason.
Good for: bots with thousands of users, media processing, Telethon or Pyrogram clients with larger caches, and anything where you want PostgreSQL’s JSONB and richer features. One-click restore turns a bad migration or accidental deletion into a minor inconvenience.
Ultra — for serious deployments
4 GB of RAM, four cores and 20 GB of storage, plus three features aimed at larger operations:
- Redis, alongside MySQL and PostgreSQL — ideal for FSM and session storage, caching and rate limiting.
- Multiple bots per server, run under a process manager.
- Region choice, when your bot’s data or users need to be somewhere other than the default.
Ultra also carries a 99.99% uptime target and 24/7 priority support.
Good for: high-traffic bots, several bots under one roof, bots with a worker process for background jobs, and teams that need the stronger SLA. See running multiple Telegram bots on one server.
Matching workloads to plans
| Bot | Suggested plan |
|---|---|
| Personal utility or learning project | Free |
| Small group helper, a few hundred users | Free or Starter |
| Reminder, subscription or shop bot with a database | Starter |
| Bot with thousands of users or media processing | Pro |
| Telethon/Pyrogram client with large caches | Pro |
| High-volume bot using Redis for state | Ultra |
| Several bots, or bot plus worker | Ultra |
Signals it’s time to upgrade
Your panel graphs tell you when a plan is getting tight:
- Memory steadily above ~70% of the plan. Spikes during bursts will eventually hit the limit and the process will be restarted.
- CPU pinned at the limit during normal use — replies slow down, and media jobs queue up.
- Disk filling up with media, logs or databases. Clean up first (see handling files and media), then upgrade if data is genuinely growing.
- You need a feature: git deploy and backups (Starter), PostgreSQL and one-click restore (Pro), Redis, multiple bots or region choice (Ultra).
- Downtime now costs you. When users rely on the bot, the paid tiers’ backups and support are worth having.
Upgrading is painless
Upgrades resize your server in place. Your session files, database and environment variables stay exactly where they are — no re-login prompts for Telethon or Pyrogram clients, no reconfiguration. That makes it safe to start small and upgrade the day your graphs say so.
If you need something outside the listed tiers — more RAM, a dedicated IP, or a custom region — the team builds custom setups for larger Telegram operations.
Summary
Start on Free: it’s real hardware, runs 24/7 and fits most small bots. Move to Starter for git deploy, backups and your own database; Pro for more resources, PostgreSQL and one-click restore; and Ultra for Redis, multiple bots per server, region choice and a 99.99% target. Watch memory, CPU and disk, and upgrade in place when they tell you to.