Preparing your next deployment? Botkeep Halloween Free: 3 months of free hosting Starts 24 October 2026. The plan and code are not active yet; see the announcement for resources and details.
- A supported Node.js or Python project
- A local copy of the project with secrets removed
- A start command tested from the project root
1. Put the project at the archive root
When the ZIP is opened, Botkeep should find package.json or requirements.txt without walking through an extra outer folder. A predictable root makes runtime detection and start-command suggestions more reliable.
moderation-bot.zip
├── package.json # or requirements.txt
├── package-lock.json # when using npm
├── src/
│ └── index.js
└── README.md2. Remove local and sensitive files
- Do not include .env, tokens, SSH keys or provider credentials.
- Exclude node_modules, .venv, __pycache__, build caches and editor metadata.
- Exclude .git unless a future workflow expressly requires repository history.
- Include only the source and data the bot genuinely needs.
3. Upload, inspect and confirm
Choose ZIP in the creation wizard, select the archive, review the detected runtime and provide the start command when detection is uncertain. The archive is uploaded to the assigned server; wait for confirmation and check Files and Console.
4. Treat every update as a new revision
Keep the original project outside Botkeep, create a fresh archive for each release and retain an independent copy of persistent data. A hosting backup must never be the only copy of your source.