Host a Minecraft server on old hardware and spare machines

If you have an unused mini PC, old desktop, home server, or spare VPS, you can run a real Minecraft Java server on it without opening SSH for day-to-day operations.

Swarm Hosts gives you browser-based control over a Linux server you already own:

  • connect a host by running the Swarm Hosts agent once
  • launch Minecraft Java from the web UI
  • keep server logs, ports, and actions in one dashboard
  • avoid managing startup scripts yourself

Quick start for non-technical hosting

  1. Install and register a swarm host.
  2. Confirm the host appears in Swarm hosts and is sending heartbeats.
  3. Open Launch and pick Minecraft Java.
  4. Set a server name and basic limits, then click Launch.
  5. Open deployment details and watch the server go from pending_deploy to running.

That flow is also documented step by step in the product first deployment guide.

When this makes sense for you

  • You want to host with hardware you already own.
  • You want one browser workflow instead of hand-crafted startup commands.
  • You are okay starting with a simple, validated server experience in Early Access.
  • You want to avoid renting a separate game server provider account for your first world.

Core requirements (current)

  • A Linux host is the recommended production path. Windows 10/11 can register through the foundation agent path when Docker Desktop or another Linux-container-capable runtime is ready.
  • One available host with enough resources for your expected player count.
  • Network access from your home host to the control plane.
  • A way for players to reach your public endpoint (usually port forwarding, or relay in paid modes when available).
  • You accept current Early Access behavior and limits.

Early Access behavior

Swarm Hosts is in Early Access. Some paid conveniences are not full-time guarantees yet.

Current public scope focuses on validated launch workflows, with Minecraft Java as the flagship path. Free use is currently generous, but plan changes can occur as Early Access transitions into a paid product model.

  • Start with default or lightly customized RAM/CPU settings while you measure real usage.
  • Use online-mode=TRUE only if your account has the credentials and launcher flow you need.
  • Keep plugins/mod packs minimal for your first launch.
  • Track player join flow from the deployment detail page before sharing an address broadly.

What you get after launch

  • Direct host-to-server controls from browser actions (start, stop, restart, update limits).
  • Deployment logs and status checks without SSHing into the host.
  • Easy connection address visibility from the deployment page.
  • Backups and file-manager access through existing workflow tabs.