Reliable 24/7 Discord bot hosting for discord.js, discord.py, JDA, and every other library. Instant deploys, auto-restart on crash, git-push deploys, and encrypted env vars — on the same dedicated infrastructure we run game servers on.
Per-bot pricing based on RAM. All plans include auto-restart, 24/7 uptime, daily backups, and any runtime you want.
Our modified Pterodactyl panel gives you everything you need to manage a dedicated game server from any device.
Every server you run, on one screen. Live CPU, RAM, network, and player counts update in real time — no refresh, no terminal, no hunting through tabs. Start, stop, or restart any instance with a single click.
13 data centers across 5 continents. Pick the location closest to your players at checkout — switch anytime.
Most 'bot hosting' services are generic shared VPSs with a fancy wrapper. You get the same cold-boot, ambiguous memory caps, and surprise suspensions as any budget VPS. Our Discord bot hosting is different: a proper application-hosting runtime on the same Pterodactyl-based panel we use for game servers, tuned for long-running persistent processes instead of web requests.
Every bot runs in its own isolated process with its own file tree, its own environment variables (encrypted at rest), its own log stream, and its own resource caps. When your bot crashes, a supervisor restarts it within three seconds. When you push to Git, we pull and redeploy automatically. When your process hits an OOM, you get a panel notification, not a silent suspension.
Supported runtimes: Node.js (18–latest), Python (3.10–latest), Java (11, 17, 21), Deno, and Bun. Switch between them from a dropdown in the panel. Need a MariaDB / MySQL / PostgreSQL / Redis add-on? One click, credentials auto-injected into env vars. Need a dedicated IPv4 for outbound API calls? Fleet plan includes one.
“Moved our community bot here after our VPS kept OOM-ing. Auto-restart and memory alerts caught two memory leaks in the first week.”
“discord.py bot with a MariaDB backend — set up in 10 minutes from the panel, no Docker wrangling.”
“We run four bots for different servers. One plan, one panel, four separate process folders. Beats paying for four VPSs.”
“The git pull button in the panel is genuinely nice. Push to main, click deploy, bot restarts. That's the workflow.”
“Support actually understood what a Discord gateway intent is when my bot started crashing after a privileged-intent change.”
“Uptime has been 100% in six months. The one time it crashed, the auto-restart had it back up in three seconds.”
Node.js (18, 20, 22, latest), Python (3.10, 3.11, 3.12, latest), Java (11, 17, 21), Deno, and Bun. Switch runtimes per bot from the panel dropdown — no sysadmin work required.
Three options: (1) drag-and-drop your bot's folder into the in-browser file manager, (2) paste a Git URL and we pull / redeploy on every push, or (3) SFTP upload. All three work on all plans.
Yes. Node.js runtimes from 18 through latest are preinstalled with npm and yarn. Package installs happen automatically on deploy — or you can run npm commands manually from the live console.
Yes. Python 3.10 through latest, with pip and pipenv preinstalled. requirements.txt installs automatically on deploy.
Yes — that's the whole point of dedicated bot hosting. Auto-restart kicks in within three seconds if the process exits. Scheduled restarts can be configured for daily refreshes if your bot has memory leaks you're still debugging.
A simple slash-command bot runs in 128 MB. Bots with music streaming, image processing, or large in-memory caches want 512 MB–1 GB. The Guardian plan (2 GB) handles community bots with databases and web dashboards attached.
MariaDB, MySQL, PostgreSQL, and Redis are available as one-click add-ons on Sentinel and above. Credentials and connection strings appear in the panel automatically — no manual setup.
Yes. Sentinel supports up to 3 bot instances, Guardian up to 10, Fleet is scale-limited. Each bot runs in its own process with its own files, env vars, and logs.
Environment variables are stored encrypted and only exposed to the process — not visible in the panel UI after save. File access is isolated per bot. We never log env var values.
Yes. Privileged intents are a Discord-side verification, not a hosting setting. Once your bot is verified with Discord, our hosting has no intent restrictions — MESSAGE_CONTENT, GUILD_MEMBERS, and GUILD_PRESENCES all work.