Guide
How to Deploy a Telegram Bot That Runs 24/7
Deploy your bot to a cloud platform using a CLI. Set your bot token as an environment variable, deploy with one command, and your bot stays online permanently. For webhook-based bots, the deployment gives you an HTTPS URL that Telegram can send updates to.
The problem
Your Telegram bot works on your local machine but dies when you close the terminal. Telegram bots need a persistent server to receive updates, either via long polling or webhooks. Running it on your laptop is not production-ready.
Long polling vs webhooks
Telegram bots can receive updates two ways. Long polling: your bot repeatedly asks Telegram for new messages. Simple but your process must stay running. Webhooks: Telegram sends updates to your HTTPS URL. More efficient but requires a public URL with SSL. Cloud deployment gives you both options: a persistent process for long polling, and an HTTPS URL for webhooks.
What you need for production
A persistent process (for long polling) or an HTTPS endpoint (for webhooks), environment variables for the bot token, automatic restart on crash, and log access. Memory: 128MB-256MB for most bots. If your bot uses AI (calling OpenAI, running local models), you may need 512MB-1024MB.
Approaches compared
Platform CLI (CreateOS, Railway, Fly)
Pros
- One-command deploy with HTTPS URL
- Supports both polling and webhooks
- Environment variables for bot token
- Auto-restart
Cons
- Monthly cost for persistent process
Best for: Most Telegram bots, especially webhook-based
Serverless (Vercel, Cloudflare Workers)
Pros
- Free for low traffic
- Auto-scales
Cons
- Webhook only (no long polling)
- Cold start delays
- Timeout limits
Best for: Simple command-response bots with low traffic
VPS with systemd or pm2
Pros
- Cheap
- Full control
Cons
- Manual SSL for webhooks
- Manual process management
Best for: Developers comfortable with Linux server administration
Deploy a Telegram bot with CreateOS CLI
Here is how to do it step by step using CreateOS CLI.
Install the CLI
Single binary for macOS and Linux.
Deploy your bot
Deploys your bot and gives you an HTTPS URL for webhooks.
Set the bot token
Get your token from @BotFather. Store it as an environment variable.
Set up the webhook (optional)
Point Telegram to your deployed URL. All updates are now sent to your server automatically.
Frequently asked questions
Should I use long polling or webhooks?
How much does it cost to host a Telegram bot?
Can I deploy a bot that uses AI?
Related guides
How to Deploy from Your Terminal
Modern CLI tools let you deploy directly from the terminal with a single command. No browser, no dashboard, no clicking. Push code, see build logs stream in real time, and get a live URL printed back to your terminal.
Read guideHow to Deploy an AI Agent to Production
Deploy your AI agent as an API service. Package it as a standard HTTP server (Express, FastAPI, Flask), deploy with a CLI command, and get a live URL. The agent becomes a callable endpoint that other applications, users, or even other agents can interact with.
Read guideHow to Deploy a Discord Bot to Production
Deploy your bot as a persistent process on a cloud platform. The bot connects to Discord's gateway on startup and stays connected. Use a CLI to deploy in one command, set your bot token as an environment variable, and the bot stays online permanently.
Read guide100,000+ Builders. One Workspace.
Get product updates, builder stories, and early access to features that help you ship faster.
CreateOS is a unified intelligent workspace where ideas move seamlessly from concept to live deployment, eliminating context-switching across tools, infrastructure, and workflows with the opportunity to monetize ideas immediately on the CreateOS Marketplace.