Minecraft: Java
Vanilla, Paper, Spigot or Purpur from a single image, with the jar and version chosen in startup settings.
Game serverChecking live status…
Game worlds, proxies, bots and small services — running on a real fleet you can inspect, managed from one control panel instead of a pile of disconnected tools.
01 — The fleet
Every number below is read from the same monitoring export that powers status.plugged.host. The panel probes each node every minute and publishes the result — aliases and metrics only, never hostnames or addresses.
Independent machines, each health-checked once a minute.
Total scheduling budget across the fleet.
— right now.
— right now.
02 — What you can run
Pick one when you create a server and the panel installs it for you. Game servers get their own port; the generic runtimes are there for bots, APIs and anything else you write yourself.
Vanilla, Paper, Spigot or Purpur from a single image, with the jar and version chosen in startup settings.
Game serverThe official Bedrock dedicated server, for players on console, mobile and Windows.
Game serverPut a proxy in front of several Minecraft servers and move players between them without a reconnect.
ProxyCFX roleplay servers. These get a second port automatically so txAdmin comes up alongside the server.
Game serverA generic runtime for Discord bots, web APIs and anything else that starts with a package manifest.
RuntimeBots, scrapers, schedulers and small services, with your dependencies installed on boot.
RuntimeBuild and run a compiled service without maintaining a toolchain on your own machine.
RuntimeThe Rust toolchain image, for services where you want the compiled binary doing the work.
Runtime03 — Your allocation
New accounts get the allocation on the right. CPU, memory and disk are a pool: spend it on one large server or spread it across several small ones, however you like. There's no cap on how many servers you create — only on the total resources they hold.
Allocations depend on available capacity and can change as the fleet does, as set out in our Terms. They're a ceiling, not a performance guarantee.
04 — The control panel
Everything below lives behind a single sign-in at panel.plugged.host. Scroll to walk through it.
Start, stop, restart or kill a server and watch its output stream in as it happens. CPU, memory and disk usage sit next to the console so you can see the cost of what you just did.
Browse and edit configuration in place, upload a world or a build, unpack archives server-side, and pull files straight from a URL. When the browser is the wrong tool, connect over SFTP with your panel credentials.
Create up to five MariaDB databases per server and get the credentials immediately. Add extra network ports when one isn't enough — a plugin server, a voice bridge, a metrics endpoint.
Keep up to five backups per server and restore or download any of them. Schedules run the boring work for you on a cron expression: restart overnight, back up before a patch, send a command on a timer.
Invite subusers and grant only the permissions they need — console but not files, backups but not deletion. Every action lands in an activity log, so a shared server stays answerable.
05 — Operations in the open
The panel probes the website, itself and every node on a one-minute schedule, then writes the result to a static feed.
Per-node CPU, memory and storage are published as numbers. A node above 90% utilization is reported as degraded, automatically.
Open incidents override component status, and every update stays visible afterwards — including over RSS.
The public feed carries node aliases and metrics only. Hostnames, addresses and port allocations never leave the panel.
Fetching recorded uptime from the monitoring feed.
Fetching recorded uptime from the monitoring feed.
06 — Straight answers
Yes — the service is provided without charge today, and nothing here authorizes a recurring payment. Capacity is finite, so allocations can be adjusted or reclaimed to keep the fleet healthy. If paid plans ever arrive, they'll come with their own terms shown before you buy.
Email and password, or Discord. You can add a passkey or a two-factor app to your account afterwards. Registration and sign-in are protected by Cloudflare Turnstile, and both ask you to accept the current Terms and Privacy Policy.
Often, yes — the Node.js, Python, Go and Rust images are general-purpose, so anything you can start from a repository will usually work inside your allocation. Crypto mining and similar workloads need written permission first; the Acceptable Use Policy has the full list of what's off-limits.
You get five backup slots per server and can restore or download any of them, but treat them as a convenience rather than an archive. Keep an independent copy of anything you'd hate to lose — we say the same thing in the Terms, and we mean it.
plugged.host is operated from Paris, France. Support happens in our Discord — open a private ticket for anything involving your account, and keep credentials and personal data out of public channels.
Ready when you are
Create an account, pick an image, and you'll have a server with an address in a couple of minutes. Bring questions to Discord — someone is usually around.