Deployment guide
How to deploy a Discord bot from GitHub
A practical Deploy Hatch workflow for taking a Discord bot repository from GitHub to a persistent running process.
Free beta · one project · no credit card required
GitHub to running workload.
A short path from source code to something you can operate.
Connect GitHub
Sign in, connect your GitHub account, and choose the repository you want to run.
Configure and deploy
Deploy Hatch detects common runtime settings and gives you control over build, start, revision, and environment configuration.
Keep it running
Watch deployment and application logs, then restart, stop, redeploy, or open public web workloads from the dashboard.
1. Prepare the repository
Make sure the bot can start from a clean checkout with its dependencies declared and a deterministic start command. Never commit your Discord bot token or other secrets to Git.
2. Create the Deploy Hatch project
Sign in to Deploy Hatch, connect GitHub, select the bot repository, and create the project. Review the detected runtime/build/start configuration before deploying.
3. Add environment variables
Add the variables your bot needs through the project environment-variable interface rather than hard-coding credentials in source.
4. Deploy and watch the logs
Start the deployment and use the build/application logs to verify dependency installation and bot startup. A successful deployment should transition to a running workload.
5. Ship updates
When you change the bot, deploy the desired branch or revision again. Use deployment history and runtime controls when you need to inspect, restart, stop, or redeploy the workload.
Put a real workload through it.
Connect GitHub, deploy, and see whether the workflow fits your project.