---
title: "Deploy Python Telegram Bot"
description: "[Jul'26] 1-Click Telegram bot setup with commands, echo & menu buttons"
category: "Starters"
url: https://railway.com/deploy/python-telegram-bot
---

# Deploy Python Telegram Bot

[Jul'26] 1-Click Telegram bot setup with commands, echo & menu buttons

**[Deploy Python Telegram Bot on Railway](https://railway.com/template/python-telegram-bot)**

- **Creator:** codestorm
- **Category:** Starters
- **Total deploys:** 266

## Template content

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18

### python-telegram-bot https://devicons.railway.app/telegram

- **Source:** codestorm-official/python-telegram-bot

### Redis https://cdn.sanity.io/images/sy1jschh/production/0ce0bfdcfbdbf69662b1116671f97c2dd788b655-157x157.svg

- **Image:** redis:8.2.1
- **Start command:** `/bin/sh -c "rm -rf $RAILWAY_VOLUME_MOUNT_PATH/lost+found/ && exec docker-entrypoint.sh redis-server --requirepass $REDIS_PASSWORD --save 60 1 --dir $RAILWAY_VOLUME_MOUNT_PATH"`

## Documentation

# Deploy and Host Python Telegram Bot on Railway

Python Telegram Bot is a starter Telegram bot built with `python-telegram-bot`. It includes ready-to-use commands, echo replies, persistent chat menu buttons, fallback handling for unknown commands, environment-based configuration, and optional PostgreSQL and Redis integration.

This template is ideal for quickly launching a Telegram bot that works immediately after adding your bot token. For more advanced use cases, you can connect PostgreSQL to persist user data and Redis to enable lightweight caching and per-user message counters.

![](https://raw.githubusercontent.com/codestorm-official/python-telegram-bot/refs/heads/main/img/bot.png)

## About Hosting Python Telegram Bot

Hosting a Python Telegram Bot means running a long-lived Python process that connects to Telegram, listens for incoming messages, and responds through the Telegram Bot API.

This template uses environment variables for configuration, so sensitive values such as your Telegram bot token, database connection string, and Redis connection string stay separate from the codebase. After deployment, the bot starts automatically and keeps running as a Railway service.

The bot uses long polling, so you do not need to configure a webhook or public domain. Once the `BOT_TOKEN` variable is added, the bot can respond to commands, normal text messages, and menu button interactions.

PostgreSQL and Redis are optional. If `DATABASE_URL` and `REDIS_URL` are available, the bot will connect to them on startup. If they are missing, empty, or unreachable, the bot logs a warning and continues running with that backend disabled. This makes the template simple for quick testing, but still flexible enough for production-oriented bot development.

## How to Edit

After deploying this template, the app is already running on Railway. You can open the generated Railway domain to test the starter app immediately.

If you want to customize the source code, use one of the workflows below.

### Via Railway CLI

Use this workflow if you want to edit the project locally and redeploy changes directly from your machine using Railway CLI.

1. Deploy the template.
2. Clone the repository from **Source Repo** or **Upstream Repo** in the Railway dashboard.
3. Enter the project directory:

```bash
cd python-telegram-bot
```

4. Link your local project directory to the deployed Railway project:

```bash
railway link
```

5. Check the linked project, environment, service, and repository information:

```bash
railway status
```

6. Edit the code locally.
7. Redeploy your local changes to Railway:

```bash
railway up
```

Railway will upload the current local directory and deploy it to the linked service.

### Via Git / GitHub

Use this workflow if you want to manage changes through GitHub and let Railway automatically redeploy after every push.

1. Deploy the template.
2. Open **Source Repo** or **Upstream Repo** from the Railway dashboard.
3. Fork the repository to your own GitHub account.
4. Clone your fork locally:

```bash
git clone 
cd python-telegram-bot
```

5. Edit the code locally.
6. Commit and push your changes to your fork:

```bash
git add .
git commit -m "Customize Python Telegram bot"
git push origin main
```

7. In Railway, change the service **Source Repo** to your fork if Railway does not automatically create or link it.
8. After the service is connected to your fork, future pushes to the repository can trigger automatic redeployments.

## Common Use Cases

* Launching a simple Telegram bot with commands and menu buttons
* Creating a support, community, or personal automation bot
* Building a base project for custom Telegram bot features
* Storing Telegram user data with PostgreSQL
* Adding lightweight Redis caching to bot responses
* Tracking simple per-user message activity
* Creating a Railway-ready Telegram bot starter with optional data stores

## Dependencies for Python Telegram Bot Hosting

* Python 3.10 or newer
* `python-telegram-bot`
* `python-dotenv`
* `asyncpg`
* `redis`
* Telegram bot token from `@BotFather`
* PostgreSQL, optional
* Redis, optional

### Deployment Dependencies

* [Telegram BotFather](https://t.me/BotFather) - Create a Telegram bot and get your `BOT_TOKEN`
* [python-telegram-bot Documentation](https://docs.python-telegram-bot.org/) - Library documentation
* [Telegram Bot API](https://core.telegram.org/bots/api) - Official Telegram Bot API reference
* [PostgreSQL](https://www.postgresql.org/) - Optional persistent data store
* [Redis](https://redis.io/) - Optional cache and counter store

## Implementation Details

This template includes a persistent reply keyboard that appears after `/start` and stays available in supported Telegram clients.

| Button  | Action                           |
| ------- | -------------------------------- |
| `Help`  | Show available commands          |
| `About` | Show short bot information       |
| `Ping`  | Check whether the bot is running |

The bot also includes these commands:

| Command  | Description                      |
| -------- | -------------------------------- |
| `/start` | Show the welcome message         |
| `/help`  | Show available commands          |
| `/about` | Show short bot information       |
| `/ping`  | Check whether the bot is running |

### Optional PostgreSQL Integration

PostgreSQL is used to persist Telegram user data.

When `DATABASE_URL` is configured, the bot creates a `users` table automatically on first run. The `/start` command inserts a new user or updates an existing user with the latest username, first name, last name, and last seen timestamp.

If PostgreSQL is not configured, the bot still runs normally. The `/start` command still replies to the user, but user data is not persisted.

### Optional Redis Integration

Redis is used for lightweight caching and per-user message counters.

When `REDIS_URL` is configured:

* `/ping` can return a cached response for a short period.
* Echoed text messages increment a per-user message counter.
* Redis-backed data survives across bot updates while Redis is available.

If Redis is not configured, the bot still runs normally. The `/ping` command replies with a plain pong response, and the message counter falls back to in-memory behavior.

### Data Store Behavior

PostgreSQL and Redis are optional by design.

If either backend is missing, empty, or unreachable, the bot logs a warning and continues running. This allows the same template to work for:

* Minimal Telegram bot deployment
* Local development
* Railway deployment with only `BOT_TOKEN`
* More advanced deployment with PostgreSQL and Redis attached

Connections are pooled and reused across updates, then closed cleanly on shutdown.

### Environment Variables

| Name           | Required | Default | Description                                        |
| -------------- | -------- | ------- | -------------------------------------------------- |
| `BOT_TOKEN`    | Yes      | -       | Bot token from `@BotFather`                        |
| `DATABASE_URL` | No       | -       | PostgreSQL connection string for user persistence  |
| `REDIS_URL`    | No       | -       | Redis connection string for caching and counters   |
| `LOG_LEVEL`    | No       | `INFO`  | Logging level, such as `DEBUG`, `INFO`, or `ERROR` |

## Why Deploy Python Telegram Bot on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you do not have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Python Telegram Bot on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your bot service, databases, cache, AI agents, and more on Railway.

## Similar templates

- [open-excalidraw](https://railway.com/deploy/open-excalidraw) — Self-hostable collaborative drawing built on Excalidraw
- [caring-vibrancy](https://railway.com/deploy/caring-vibrancy) — Deploy and Host caring-vibrancy with Railway
- [Appsmith](https://railway.com/deploy/appsmith-1) — Low-code platform for internal tools, dashboards, and admin panels.

Open this page in a browser: https://railway.com/deploy/python-telegram-bot