Use Telegram Serverless

Build, ship, and scale simple or full-stack Telegram bots and Mini Apps directly inside Telegram's cloud—with zero servers to manage.

Powered by Telegram Serverless (tgcloud): instant V8 JavaScript (ES Module) isolates, a built-in SQLite database (sdk/db), native Bot API & HTTP clients (sdk/api, sdk/fetch), authenticated Mini App RPC endpoints (Telegram.WebApp.Serverless.call), and built-in static hosting (tgcloud.ai).

When to Use

• Any Telegram Serverless project (simple or full-stack): You're starting a quick single-handler bot, building a lightweight Mini App, or scaling a full-stack app with Telegram Serverless, tgcloud, @tgcloud/cli, @tgcloud/bot, tgcloud/, or tgcloud.jsonc.
• V8 JavaScript backend & SQLite data: You want to create or update bot handlers (tgcloud/handlers/*.js), authenticated Mini App endpoints (tgcloud/endpoints/*.js), shared ES modules (tgcloud/lib/**/*.js), SQLite schemas & queries (tgcloud/schema.js), or Mini App static hosting (https://app<app_id>.tgcloud.ai/).
• Simple commands or rich production flows: You're implementing anything from /start commands, inline keyboards, and outbound sdk/fetch calls to conversational state machines, 64-byte callback routers, Telegram Stars (XTR) payments, inline queries, progressive draft replies (sendMessageDraft), or Telegram.WebApp.Serverless.call frontend integrations.
• Safe cloud operations & debugging: You need code review, security auditing, zero-downtime SQLite schema migrations (tgcloud migrate), remote sandbox testing (tgcloud run), live deployment (tgcloud push), webhook sync, or local/cloud conflict recovery.

When Not to Use

• A Telegram bot is intentionally hosted on a VPS, Docker container, Cloudflare Workers, AWS Lambda, Vercel, or another non-Telegram runtime (using frameworks like grammY, Telegraf, or aiogram). Do not migrate external bots to Telegram Serverless unless explicitly asked.
• The task only involves generic frontend styling unrelated to Telegram Mini App SDK integration or tgcloud.jsonc static hosting.
• A requested feature requires a capability not supported by the Telegram Serverless V8 isolate runtime (such as raw TCP sockets, background cron daemons, native Node.js C++ addons, or filesystem persistence outside SQLite). Explain the platform constraint first before proposing workarounds or external architectures.