Public rates retrieved 2026-11-12 from official vendor pricing pages cited below; promotional & renewal prices may change — always verify exact specs, term length, and renewal rates on the vendor’s official checkout page.
1. Aligning VPS Region with Telegram DC2/DC4 (Europe) and DC5 (Singapore) on BotFoundry
Telegram anchors its core webhook dispatcher and European user shards in Europe (DC2/DC4) while routing Southeast Asian accounts through Singapore (DC5). Selecting Frankfurt/London or Singapore minimizes TLS handshake round-trips.
2. Preventing TDLib Media Cache from Filling 100 GB NVMe Disks in BotFoundry Deployments
Local telegram-bot-api writes every 500 MB–2,000 MB video transfer into /var/lib/telegram-bot-api. Schedule a systemd timer (`find /var/lib/docker/volumes/tg_cache -type f -mmin +360 -delete`) every 6 hours so temporary media never exhausts NVMe inodes.
3. Caching WebApp.initData HMAC Sessions in Redis for Viral Mini-Apps on BotFoundry
Campaign traffic spikes send thousands of concurrent Mini-App requests; verify the HMAC-SHA256 initData signature once, issue a short-lived Redis session token, and front PostgreSQL 16 with PgBouncer transaction pooling.
Why does BotFoundry recommend switching Telegram bots from getUpdates polling to HTTPS webhooks?
Long-polling serializes update fetches and wastes idle sockets; terminating HTTPS on port 443 via Caddy with X-Telegram-Bot-Api-Secret-Token validation pushes updates concurrently to uvloop/Bun workers.
Can BotFoundry users offload Mini-App static HTML/JS bundles to ChemiCloud?
Yes — hosting static React/Vite Mini-App assets on a $2.95/mo ChemiCloud LiteSpeed plan leaves 100% of your Ubuntu KVM VPS memory and CPU dedicated to API and database workers.
Which inbound TCP ports does Telegram officially accept for webhooks?
Telegram dispatches HTTPS webhooks exclusively to ports 443, 80, 88, or 8443 backed by a trusted TLS certificate (such as automated Let’s Encrypt).
BotFoundry memory math for headless Chromium BrowserContexts, Docker --shm-size=2g shared memory pools, tini zombie reaping, and flat-bandwidth KVM nodes.