FREE DISCORD BOT HOSTINGNODE + PYTHON

Free hosting for your Discord bot.

Deploy from GitHub or ZIP, protect your token and run up to two bots for free—without managing a server.

Sources
GitHub / ZIP
Runtimes
Node.js / Python
Free plan
Two bots included
MKmoderation-keepermain · 8d4f21a
Running
CURRENT DEPLOYMENT

Bot is connected.

Live resourcesjust now
Memory184 / 512 MB
CPU7 / 50%
Storage220 MB / 1 GB
Environment
DISCORD_TOKEN Protected
NODE_ENVproduction
Live output streaming
systemworkload assigned to node eu-04
botLogged in as Keeper#0421
readyServing 12 communities
01PUSH
02BUILD
03ISOLATE
04RUN
DEPLOYMENT, WITHOUT THE DETOUR

From commit to connected.

Botkeep handles the repetitive infrastructure between working code and a bot that stays online.

01

Bring the code

Connect a GitHub repository or upload a ZIP. Botkeep detects Node.js and Python projects for you.

02

Keep the secret

Add the Discord token once. It is encrypted at rest and kept out of source, builds and logs.

03

Start the bot

We build in isolation, apply resource limits and start the bot in its own private runtime.

Import a repository
or
Upload a ZIP

Start command detected or configured by you.

A PROTECTED RUNTIME

Your token goes only where it needs to.

Tokens are encrypted at rest and exposed only to your bot's isolated runtime. They stay out of source code, build artifacts and dashboard logs.

Read the security model
BOTKEEP NODEpolicy enforced
ISOLATED RUNTIMEnon-root
bot process
0.5 vCPU 1 GB read-only base
01

Separated

Each bot runs as a non-root process inside its own restricted environment.

02

Bounded

Memory, CPU, storage and process limits are applied before the bot starts.

03

Observable

Health, resource use and restarts remain visible without exposing the secret.

DAY-TO-DAY CONTROL

Everything useful. Nothing server-shaped.

The controls are designed around the bot you are running, not the machine underneath it.

01

Readable live logs

Follow output as it happens, with timestamps and deployment context that make failures easier to trace.

02

Automatic recovery

A crashed process restarts with controlled backoff. You get the status, the cause and the useful last lines.

03

Resources in view

Memory, CPU and storage stay visible, so limits are predictable instead of hidden behind infrastructure jargon.

04

Deploy on push

A new revision builds before it replaces the running version. Failed builds leave the healthy bot alone.

BOTKEEP PRICING · FREE DURING BETA

The first two bots are on us.

Enough room for a moderation bot, a community utility or the project you are still shaping.

Reserve beta access
Memory512 MBper bot
Compute0.5 vCPUper bot
Storage1 GBpersistent
DeploysGitHub + ZIPincluded
PLANS & CAPACITY

A free start, with more room to come.

The beta plan is confirmed. Paid limits and prices are still being shaped around real workloads and will be published before launch.

02Planned after beta

More capacity

Pricing soon

For builders who outgrow two bot slots or need larger runtime limits as their communities grow.

  • Additional bot capacity
  • Higher resource options
  • The same protected runtime model
  • Final limits published before launch
Join product updates
03Discussed case by case

Custom capacity

On request

For communities with unusual capacity requirements that need to be reviewed before beta access.

  • Capacity scoped around the workload
  • Node.js and Python runtimes
  • GitHub and ZIP source support
  • Availability reviewed with the team
Discuss requirements

No payment is collected during private beta. Paid plan names, limits and prices remain provisional until they are announced.

BOTKEEP PRIVATE BETA

Code the bot.
We'll keep it running.

Botkeep is preparing for a limited private beta. Dashboard access will open in controlled waves.

No card required during beta.