Pick a plan for your bot
Background processes, dependencies and the difference between a bot and a website plan.
Start with the process
Each Bot plan covers one background bot or worker. Starter suits a small community bot, Plus has more memory for integrations, and Pro gives heavier jobs more CPU and storage. Resource needs depend on your code, dependencies and activity.
Check how the bot connects
The proposed runtimes are Node.js and Python. Bot plans support outward connections and polling. If you need a public HTTP or webhook endpoint, use a Website plan; if you need extra system packages or several processes, consider a VPS.
Keep secrets in settings
Store bot tokens in environment variables, not in source files or public repositories. Review logs without printing tokens. Automatic process restart and start/stop controls are planned; these do not guarantee that application code is error-free.
Understand this preview
You can compare plans and review their details. No bot starts until an active service and its runtime node are connected. Monthly transfer and backup slots are proposed limits; confirm service availability in your account.