Paste your BotFather token, write a little JavaScript, hit Run. Botledge runs your bot on Cloudflare's global edge network — no VPS, no servers to babysit, no monthly bill.
Works with any bot token from @BotFather. Nothing to install.
Botledge gives your code a small, friendly API — bot.command(), bot.on(), and ctx.reply(). Everything runs the instant Telegram sends an update.
Free. Unlimited bots, no card.
Always on — Telegram pushes updates to us.
Replies from the nearest Cloudflare node.
If you can paste a token, you can host a bot here.
Open Telegram, talk to @BotFather, run /newbot and copy the API token it gives you.
Add a bot on Botledge, paste the token and write your JavaScript in the built-in editor.
Botledge registers the webhook and your bot goes live 24/7. Message it on Telegram to check.
One click registers your Telegram webhook. No nginx, no SSL, no PM2.
ctx.store keeps per-user scores and settings in SQLite (D1) — no database to set up.
See every reply and error your bot makes, right in the dashboard.
Call any API from your bot — weather, AI models, payment gateways, anything over HTTPS.
Your token and code are yours. Every webhook is verified with a secret token.
Host as many bots as you want from one account, all from the same dashboard.
Botledge runs on Cloudflare Workers, so your code is plain JavaScript with fetch and the Botledge bot API. That means:
Async JavaScript, fetch(), the bot API, ctx.store, timers within the request, and any HTTPS API.
Node core modules (fs, http, child_process), require(), long polling, and always-on background loops. Write those and you'll get a clear error.
Yes. Botledge runs on Cloudflare's free tier, so there's no charge and no card. Fair-use limits apply per Cloudflare's own free plan.
Serverless functions can't run a 24/7 getUpdates loop. Telegram pushes each update to your bot's URL instead — that's what makes free 24/7 possible.
Any browser/edge JavaScript. Node-only code (files, sockets, native modules) won't run and Botledge will tell you why.
In a Cloudflare D1 database bound to your own deployment. You own the whole stack.