Botkeepa NexNode product
Get 2 bots free
DISCORD.PY HOSTING

discord.py hosting,
without managing a Python server.

Package a Python Discord bot with requirements.txt, a direct startup command and secrets supplied through the runtime environment.

Prepare a Python botOpen the Python deployment guide
01 · RuntimePythondiscord.py projects
02 · Startmain.pysingle entry point
03 · Sources2GitHub or ZIP
04 · Free slots2per account
A FOCUSED HOSTING MODEL

Everything the promise needs to mean.

01

Declare requirements explicitly

List discord.py and production dependencies in requirements.txt. Use compatible version ranges or pinned versions instead of relying on an undeclared local environment.

02

Use one direct process

A command such as python main.py gives the runtime a clear lifecycle and makes crash output easier to understand.

03

Read secrets from os.environ

Keep the Discord token out of main.py, .env files and uploaded archives. Fail clearly when a required environment value is missing.

04

Keep state deliberately

Use the persistent storage allocation only for data that must survive a restart, and maintain an independent copy of anything important.

INPUT → RUNTIME

The discord.py deployment contract

01

requirements.txt

The dependency list travels with the project.

02

main.py

One explicit entry point starts the bot process.

03

DISCORD_TOKEN

os.environ supplies the secret outside source code.

04

Process output

Tracebacks and diagnostic logs remain available for debugging.

READ BEFORE DEPLOYING

Important answers.

Open the full FAQ
What happens if my bot crashes?

The production design records the process exit, keeps the relevant logs visible and retries with backoff so a broken bot cannot restart in a tight loop forever. Repeated failures move the bot into a crashed state for diagnosis instead of hiding the problem. The current panel only simulates this flow.

How do backups work?

The plan model includes one backup per bot on Free, three on Plus and five on Pro, with intended retention of 7, 30 and 45 days respectively. A backup is a recovery aid, not permanent archival storage. Keep an independent copy of important code and data. The production restore workflow must be tested before these limits are represented as operational.

Read the backup terms
Are CPU, RAM and the physical servers shared?

The underlying nodes are multi-tenant. Each bot receives an enforced allocation or cap rather than dedicated physical hardware. On Free, the intended per-bot limits are 512 MB RAM, 0.5 vCore and 1 GB storage. CPU remains a shared scheduling resource, so a displayed maximum is not a dedicated core or a guarantee of constant peak performance.

Can I host a real bot in the current public prototype?

Not yet. The current dashboard is a frontend prototype with local mock data. Do not enter a real Discord token, private repository or production file. Live Botkeep API, provisioning, authentication, database and payment integrations are not connected.

Two free bot slots. One clear starting point.

Choose Node.js or Python, bring a GitHub repository or ZIP, and review the exact limits before the beta opens.