Host a Discord bot 24/7 by saying “deploy this” in Claude, Cursor or any MCP editor. The folder ships, the gateway connection is held open, and the bot stays online after you close the laptop. No VPS, no panel, no Dockerfile, no API key.
Free for 7 days, then $3/mo. No card to start.
ONE COMMAND · GATEWAY HELD OPEN · RESTARTS ITSELFThe gateway connection is held for as long as your app is alive, and your app is alive continuously. When it crashes it comes back on its own, usually before anyone opens a ticket.
Say “deploy this app” in Claude or Cursor. We bundle the folder and ship it.
Paste the app token from the Discord Developer Portal. It’s encrypted and never shown again.
Crashes restart automatically. If it crash-loops we stop and tell you instead of hiding it.
It is a coffee, once. It is also the difference between an app your server relies on and one that is a running joke in #general. If it is genuinely just for you, the first one is free for 7 days with no card.
You can, and it works until your app is idle for fifteen minutes, which for most servers is most of the night. Free tiers suspend idle processes on purpose. A waiting app looks idle to them.
No. You point Claude Code, Cursor, Codex or any MCP editor at the folder and say deploy. There is no Dockerfile, no SSH, and no process manager to configure.
Host a Discord bot 24/7 without a VPS or a Dockerfile. Your bot opens a gateway connection and holds it, which needs a process that never sleeps — not a serverless function that spins down when nobody calls it.
Connect once, then deploy, read logs, restart and roll back by asking. No API key to copy.
No metering, no surprise invoice. Seven days free to start, and no card until you keep it.
SOLO for discord bots. A gateway bot idles at about 90MB. Solo gives it 512MB, which is room to spare for one bot.
Here it is $3 a month for one bot, billed per bot rather than per request, with nothing metered — no charge for uptime, bandwidth or commands served. The first 7 days are free and need no card. A VPS elsewhere is usually $5–6 for the smallest instance, and you administer it yourself.
You can, but free tiers suspend processes that look idle, and a bot waiting on the gateway looks idle to them — which is why free-hosted bots go offline overnight and come back when someone visits the dashboard. If the bot only has to work while you are watching, free is fine. If a server depends on it, it is not.
Not until roughly 2,500 servers. Discord only requires it past that. Below it, one process is fine and simpler.
Both, unchanged. Node 22 and Python 3.11 are the runtimes, so discord.js, discord.py, JDA, serenity, DSharpPlus and Discord4J all run as written. Dependencies install from your package.json or requirements.txt — there is nothing to declare beyond the file you already have.
discord.com/developers → your application → Bot → Reset Token. Turn on the intents your code uses while you are there, or the bot will fail to log in. Paste the token in as an environment variable; it is encrypted and never shown again.
Yes. Slash commands are registered with Discord, not with us, so they survive a redeploy and a restart. If they stop responding it is the bot being offline rather than the commands being lost, which the logs will show.
Usually a missing environment variable — the thing your .env had but the deploy didn't. Ask your agent to read the logs; it's almost always in the first few lines. The second most common cause is an intent enabled on your machine but not in the Developer Portal.
Yes, and nothing about the code changes. Point your agent at the existing folder and say deploy. Set the same environment variables you had before, and remove any keep-alive ping or uptime-robot workaround — it was there to defeat an idle timeout that does not exist here.
$3 a month, always on. First one free for 7 days, no card.
Cursor and VS Code open and install it themselves. For Claude Desktop or claude.ai, paste the URL under Settings → Connectors → Add custom connector.