A free tier you can understand
Each Free bot uses a published profile: up to 512 MB RAM, 0.5 vCore and 1 GB persistent storage. The limits are visible before deployment.
Run two Discord bots on the Free plan with defined per-bot limits, no scheduled idle sleep and no periodic server-renewal ritual.
Each Free bot uses a published profile: up to 512 MB RAM, 0.5 vCore and 1 GB persistent storage. The limits are visible before deployment.
The runtime model does not schedule an idle bot to sleep simply because a community has been quiet. Maintenance and incidents can still interrupt service.
Botkeep does not ask you to click a button every few days to keep an assigned free slot. Fair use and service rules still protect shared capacity.
Move to five or ten active bots with published RAM, storage, database and backup limits when the free capacity is no longer enough.
Import a GitHub repository or choose a clean ZIP archive.
Use the focused Node.js or Python path and review the start command.
Keep DISCORD_TOKEN outside source and ordinary logs.
Use status, resource metrics and logs to understand what the bot is doing.
No. Botkeep’s Free plan is designed without a periodic manual renewal timer. You do not need to return to the dashboard just to keep an assigned slot alive. Capacity, security, fair-use and Terms enforcement still apply.
No scheduled idle sleep is part of the Botkeep runtime model. A bot may still be restarted or temporarily unavailable because of maintenance, a crash, a deployment, exhausted resources, a security response or an infrastructure incident.
No. “24/7” describes continuous operation without a commercial sleep timer or manual renewal ritual. It is not a promise of uninterrupted 100% availability. The beta has no uptime SLA unless a separate written agreement expressly provides one.
Read the service termsChoose Node.js or Python, bring a GitHub repository or ZIP, and review the exact limits before the beta opens.