Prepare the code.
Know the runtime.
Focused guides for the two supported runtimes and the two planned source workflows. Every guide separates the current local prototype from production behaviour.
The interface is functional with local demo data. Live hosting, provisioning and production security controls are not connected yet.
Choose by runtime or source.
Runtime guides explain how the process starts. Source guides explain how the same project reaches Botkeep.
Deploy a Node.js Discord bot
Prepare a discord.js project for Botkeep with a predictable start script, declared dependencies and a token read from the runtime environment.
Deploy a Python Discord bot
Package a discord.py bot with explicit dependencies, a single startup command and secrets kept out of source files.
Deploy from GitHub
Connect a repository, choose a revision and keep deployments traceable without placing credentials in code.
Deploy from a ZIP archive
Build a clean, portable archive that Botkeep can inspect without hidden local dependencies or leaked secrets.
- Keep a working copy of source and important data outside Botkeep.
- Never place a live Discord token in a repository, ZIP or support message.
- Use one non-interactive process and write diagnostic output to stdout or stderr.
- Do not assume root access, public ports or arbitrary system packages.
Understand the limits before deploying.
The FAQ covers continuous operation, shared resources, crashes, backups, fair use and data deletion.