Checking live status…

Host what you build.

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.

  • Free to use today
  • 9 nodes probed every minute
  • Open status & uptime history
9/9 nodes reporting
CPU
Memory
Storage

01 — The fleet

Capacity you can count, not adjectives.

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.

Nodes 9

Independent machines, each health-checked once a minute.

CPU threads 176

Total scheduling budget across the fleet.

Memory 1.32TB

right now.

Storage 27.5TB

right now.

02 — What you can run

Eight images, ready when you are.

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.

Minecraft: Java

Vanilla, Paper, Spigot or Purpur from a single image, with the jar and version chosen in startup settings.

Game server

Minecraft: Bedrock

The official Bedrock dedicated server, for players on console, mobile and Windows.

Game server

Velocity

Put a proxy in front of several Minecraft servers and move players between them without a reconnect.

Proxy

FiveM / RedM

CFX roleplay servers. These get a second port automatically so txAdmin comes up alongside the server.

Game server

Node.js

A generic runtime for Discord bots, web APIs and anything else that starts with a package manifest.

Runtime

Python

Bots, scrapers, schedulers and small services, with your dependencies installed on boot.

Runtime

Go

Build and run a compiled service without maintaining a toolchain on your own machine.

Runtime

Rust

The Rust toolchain image, for services where you want the compiled binary doing the work.

Runtime

03 — Your allocation

A real budget, stated up front.

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.

CPU400% of a thread — roughly four threads
400%
MemoryShared across every server you create
12,288MB
DiskShared across every server you create
51,200MB
DatabasesMariaDB, per server
5
PortsNetwork allocations, per server
5
BackupsPer server, restore or download any of them
5
ServersCapped by the resource pool, not by count
Unlimited

04 — The control panel

One place for the whole lifecycle.

Everything below lives behind a single sign-in at panel.plugged.host. Scroll to walk through it.

STEP 01

Console and power

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.

  • Live console
  • Power actions
  • Resource graphs
STEP 02

Files, in the browser or over SFTP

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.

  • Editor
  • Uploads
  • Archives
  • SFTP
STEP 03

Databases and ports

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.

  • 5 databases
  • 5 ports
  • Credentials on demand
STEP 04

Backups and schedules

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.

  • 5 backups
  • Restore & download
  • Cron schedules
STEP 05

People and accountability

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.

  • Subusers
  • Granular permissions
  • Activity log
Console and power Stream output live and act on it in the same view.
Files and SFTP Edit in place, or connect a real client when you need one.
Databases and ports Five databases and five ports per server, on request.
Backups and schedules Five restore points, plus cron jobs for the routine.
People and accountability Scoped access, with a log of who did what.

05 — Operations in the open

We publish the bad days too.

  • Checked every minute

    The panel probes the website, itself and every node on a one-minute schedule, then writes the result to a static feed.

  • Utilization, not vibes

    Per-node CPU, memory and storage are published as numbers. A node above 90% utilization is reported as degraded, automatically.

  • Incidents on the record

    Open incidents override component status, and every update stays visible afterwards — including over RSS.

  • Sanitized by design

    The public feed carries node aliases and metrics only. Hostnames, addresses and port allocations never leave the panel.

Websiteloading…

Fetching recorded uptime from the monitoring feed.

Panelloading…

Fetching recorded uptime from the monitoring feed.

06 — Straight answers

The questions people actually ask.

Is it really free?

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.

How do I sign in?

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.

Can I run something that isn't on the list?

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.

Are my backups safe?

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.

Who runs this, and where do I get help?

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

Give your next project somewhere to live.

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.