---
title: "Deploy Discord.py Bot"
description: "Python Discord bot with slash commands. Requires a Discord bot token."
category: "Bots"
url: https://railway.com/deploy/discordpy-bot
---

# Deploy Discord.py Bot

Python Discord bot with slash commands. Requires a Discord bot token.

**[Deploy Discord.py Bot on Railway](https://railway.com/template/discordpy-bot)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/discordpy-bot/manifest.json

- **Creator:** leodev
- **Category:** Bots

## Template content

### bot

- **Source:** https://github.com/leoisadev1/railway-template-discord-py-bot
- **Health check:** /health

## Documentation

# Deploy and Host Discord.py Bot on Railway

A Python Discord gateway worker using discord.py 2.7.1, `/ping` and `/info`, locked dependencies, and separate HTTP readiness/liveness endpoints. No public homepage, database, or volume is needed.

## About Hosting Discord.py Bot

The Dockerfile pins Python 3.12.14 and the uv build image by digest, installs frozen production dependencies from `uv.lock`, and runs as non-root UID/GID 10001. Keep one replica and sleeping disabled for the gateway connection.

### Required Discord setup

1. Create an application in the [Discord Developer Portal](https://discord.com/developers/applications).
2. Set `DISCORD_TOKEN` to its **Bot token**. No dummy or generated default is provided.
3. Invite it with OAuth2 scopes `bot` and `applications.commands` and permissions to send command replies.
4. Deploy, wait for command synchronization and gateway readiness, then invoke `/ping` and `/info` in Discord.
5. For guild-scoped synchronization, set optional `DISCORD_GUILD_ID` to that guild's positive snowflake ID. Omit it for global synchronization, whose propagation is controlled by Discord.

**Real Discord authentication and chat replies require a valid user-supplied bot token.** No live provider E2E result is claimed. A process responding to HTTP alone is not a working bot.

### Variables and intents

- `DISCORD_TOKEN`: required secret, no default; never commit it.
- `PORT`: internal readiness listener, default `8080`; `HOST` defaults to `0.0.0.0` inside the container.
- `DISCORD_GUILD_ID`: optional command-sync scope.
- `MESSAGE_CONTENT_INTENT`, `MEMBERS_INTENT`, and `PRESENCES_INTENT`: default `false`. Enable only when needed and after matching opt-in in the Developer Portal. Slash commands do not require privileged intents.

Synchronization replaces the chosen scope's command tree. Use a dedicated application and review command removals before deployment. Rejected intents or synchronization failures prevent successful startup.

### Health and operation

`/health`, `/healthz`, and `/ready` return 200 only with synchronized commands and a connected, ready gateway; otherwise 503. `/live` reports process liveness independently. The root and unknown GET routes return 404; public Discord HTTP interactions are not implemented. Railway checks `/health` with a 60-second allowance and restarts on failure. This deployment check is not continuous dependency monitoring.

Missing/rejected credentials, invalid guild IDs, sync/intent/bind failures, startup timeout, and unexpected gateway termination fail closed. SIGTERM/SIGINT close gateway and HTTP resources. `/ping` reports latency and `/info` reports library/bot information ephemerally. Edit `bot.py` to extend the commands. Voice support is not included.

The worker has no durable data store. Local mock-provider tests cannot verify Discord permission setup, gateway connectivity, propagation, replies, or container permissions; validate those in your own deployment.

## Common Use Cases

- Python slash-command prototypes.
- Community bots with guild-scoped development commands.
- A lightweight Discord gateway worker without public networking.

## Dependencies for Discord.py Bot Hosting

A Railway worker, real Discord Bot token, and an appropriately scoped invitation.

### Deployment Dependencies

- [Template source](https://github.com/leoisadev1/railway-template-discord-py-bot).
- [discord.py documentation](https://discordpy.readthedocs.io/).
- Python 3.12, uv, and the committed `uv.lock`.

## Why Deploy Discord.py Bot on Railway?

Railway hosts the worker with secret variables, deployment logs, healthchecks, and restart policy. Discord credentials, application permissions, and real command-delivery validation remain your responsibility.


## Similar templates

- [Telegram JavaScript Bot](https://railway.com/deploy/5lRkWa) — A template for Telegram bot in JavaScript using grammY
- [Cobalt Tools [Updated Sep ’26]](https://railway.com/deploy/cobalt) — Cobalt Tools [Sep ’26] (Media Downloader, Converter & Automation) Self Host
- [Telegram Gateway](https://railway.com/deploy/railway-telegram-gateway) — Multi-bot Telegram webhook gateway with WebSocket event streaming

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