Before you deploy
- Add
DISCORD_TOKENin Settings → Secrets. - Enable the privileged intents listed on the Overview tab.
- Verify your email address (required for deployments).
What happens
- A deployment is queued with a new version number.
- The project is built into an image in a separate build step.
- The bot starts in an isolated container with CPU, memory and process limits from your plan.
- The status changes to Online once the process is up.
Status, logs and metrics
The Logs & metrics tab shows live logs (secrets are redacted), CPU and memory usage against your plan's limit, restarts, uptime and the deployment history.
Crashes and restarts
If the bot exits unexpectedly it is restarted automatically with an increasing delay, so a crash loop doesn't hammer Discord. Use Explain an error in Settings to get a plain-language explanation of an error message.
Stopping
Stop shuts the bot down and frees a running slot on your plan. Your files and secrets are kept.