Basic
Small botsIdeal for small community bots getting started.
- 512 MB RAM
- 75% CPU (AMD EPYC)
- 5 GB NVMe Storage
- 2 Backups
- Standard Support
- Layer 7 DDoS Protection
- Auto Restart
Your Telegram bot runs 24/7 on AMD EPYC hardware with zero sleep mode. Long polling or webhooks — both just work. Session files survive every restart.
Host your bot UPI, PayPal & Cards Accepted • No Sleep Mode • Sessions PersistSame EPYC hardware on every tier. Upgrades resize in place — your session files and database stay put.
Need more RAM, a dedicated IP, or a custom region? We build tailored setups for large Telegram operations.
Prices auto-convert to your region · conversions are indicative
Ideal for small community bots getting started.
Best value for most bots.
For busy bots serving many chats at once.
Serious headroom with premium support.
Dedicated IP and serious compute for big bots.
Maximum power & features, elite support.
3-day money-back guarantee on paid plans · UPI, PayPal & cards accepted
Technical specifications for all available configurations.
| Free$0/forever | Basic$0.67/mo | PopularPro$1.12/mo | Extreme$2.15/mo | Ultimate$3.95/mo | Supreme$5.65/mo | Elite$11.33/mo | |
|---|---|---|---|---|---|---|---|
| Resources | |||||||
| RAM | 256 MB | 512 MB | 1 GB | 3 GB | 6 GB | 8 GB | 12 GB |
| Storage (NVMe SSD) | 2 GB | 5 GB | 10 GB | 20 GB | 30 GB | 50 GB | 80 GB |
| CPU Priority (AMD EPYC) | 30% | 75% | 100% | 200% | 300% | 400% | 600% |
| Protection, Network & Support | |||||||
| Dedicated IP | — | — | — | — | — | ||
| Backups | — | 2 | 3 | 5 | 10 | 20 | Unlimited |
| DDoS Protection | Layer 7 | Layer 7 | Layer 7 | Layer 7 | Layer 7 | Layer 7 | Layer 7 |
| Uptime SLA | 99.9% | 99.9% | 99.9% | 99.9% | 99.9% | 99.99% | 99.99% |
| Support Level | Community | Standard | Priority | Priority | 24/7 Premium | 24/7 Priority | 24/7 Elite |
| Network & Features | |||||||
| Global Locations | 20+ PoPs | 20+ PoPs | 20+ PoPs | 20+ PoPs | 20+ PoPs | 20+ PoPs | 20+ PoPs |
| Enhanced Security+ | — | — | — | — | — | — | |
| Start free | Choose | Choose Pro | Choose | Choose | Choose | Choose | |
Swipe to compare all plans →
Watch it respond in real time. No sleep delays, no cold starts — the moment a message arrives, your bot handles it. That's what zero sleep mode actually means.
Free PaaS hosts kill idle polling loops. Here your process is persistent, so either mode just works.
The classic. Your bot keeps an open request to the Telegram API and reacts the moment an update lands. Needs a process that never stops — exactly what you get.
Telegram pushes updates to your HTTPS endpoint. Lower idle load, instant delivery — every Kerit server gets a TLS endpoint you can register in one call.
Telethon and Pyrogram sessions live on persistent NVMe. Redeploy, upgrade, restart — your users never see a re-login prompt.
Telethon, Pyrogram, and any MTProto client stores its .session file on persistent NVMe. No re-authorization on restart or redeploy.
SQLite databases, JSON state files, and conversation history persist across restarts. Managed MySQL and Postgres available on paid plans.
Your bot token and API keys live in encrypted environment variables — never in logs, never in code. Isolated per container.
If it runs on Linux, it runs here. Session files and SQLite state survive restarts and redeploys.
Polling, webhooks, sessions, migrations — quick answers before you deploy. Still stuck? Ask on Discord.
Both work. Long polling runs perfectly because your process never sleeps. If you prefer webhooks, every server gets an HTTPS endpoint you can register with the Telegram API.
Yes. Your disk is persistent NVMe — session files, SQLite databases, and downloaded media survive restarts and redeploys. No re-login loops.
Python: aiogram, Telethon, Pyrogram, pyTelegramBotAPI. Node.js: grammY, Telegraf, node-telegram-bot-api. Java: TelegramBots. Anything that runs on Linux runs here.
Tokens live in encrypted environment variables, never in your code or logs. Each bot runs in an isolated container — no other customer can read your files or environment.
On Ultra, yes — run several bots in one server with a process manager. On smaller plans we recommend one bot per server so each gets dedicated resources.
Yes — point your git repo at a new Kerit server, copy your environment variables, and start. Most migrations finish in under ten minutes; our Discord support can walk you through it.