lodestone

Last reviewed Sep 13, 2026 · 936 words

Pterodactyl needs a panel, a database, Redis, a reverse proxy and a separate Wings daemon before you have hosted a single Minecraft world. Lodestone needs one binary. That is the entire pitch, and for a household running two or three Minecraft servers on a spare machine it is the right trade: 512 MB of overhead, a Rust core that listens on port 16662, and a dashboard that gets a Paper or Fabric server online in under 5 minutes. The cost is that it does far fewer things, and the project's pace is uneven, which I will be straight about below.

One binary, one port, no database

Lodestone Core is a single Rust process that keeps its state in a data directory as files. There is no MySQL, no Redis, and no separate agent, because the core is both the API and the thing that launches game processes. Run it as a binary on Linux, as the ghcr.io/lodestone-team/lodestone_core container with the data directory mounted, or install the desktop app, which bundles the same core behind a native window. Whichever you choose, the first start prints a setup key you paste into the dashboard to create the owner account, and from then on the web UI on port 16662 is where everything happens.

Users, permissions and multi-user access exist and are simple: an owner, then accounts you invite with per-instance rights. It is enough for a family or a small friend group, which is the audience. Put a reverse proxy with TLS in front if the dashboard is reachable from outside; the core speaks plain HTTP and WebSocket.

Minecraft first, everything else a distant second

The one-click flavour in the listing is real for Minecraft. Pick vanilla, Paper, Fabric or Forge, pick a version, and Lodestone downloads the server jar, the correct Java, and writes a working config with a memory allocation you set with a slider. Console, file browser, player list and resource graphs are all in the dashboard. Ports are whatever you assign per instance, so three servers on 25565, 25566 and 25567 on one box is routine.

Beyond Minecraft, support is a generic instance: you provide the executable or start command and Lodestone manages the process, console and files. That works, but it is not the curated egg-style catalogue that Pterodactyl or PufferPanel ship for Valheim, Terraria, Rust and the rest. If your group plays four different games, the listing's "fewer games" con is the deciding factor, not a footnote.

Macros are the feature nobody else has

Lodestone lets you write macros in TypeScript, executed by an embedded Deno runtime, that react to server events: a player joins, a chat message matches a pattern, a scheduled time arrives, resource use crosses a line. People use them for automatic restarts at 4 a.m. with a 5-minute in-game warning, for a Discord webhook when the last player leaves, for backing up the world folder when the server goes idle. On Pterodactyl this is a schedule tab plus external scripts; here it is a first-class scripting hook with access to the console stream. For a Minecraft admin who can write a few lines of JavaScript, this alone justifies the install.

The honest project-health note

The catalogue's "project pace varies" is doing polite work. Lodestone launched in 2022 with a burst of activity, and since then releases have arrived in clusters rather than on a schedule, with long quiet stretches in between. That is normal for a small team's open-source project, but it means two practical things. New Minecraft versions can lag before the one-click installer knows about them, in which case you point a generic instance at a jar you downloaded yourself. And if you hit a bug, you should expect to read the issue tracker and possibly patch it rather than wait for a fix.

None of that makes it unsafe to run. A server manager that mostly launches Java processes does not rot quickly, and the AGPL-3.0 code is there to fork. It does make it a poor choice for anyone selling hosting or running servers for people who will complain when something is stale.

Pterodactyl, Crafty and PufferPanel: where each wins

Three real alternatives in the game server category. Pterodactyl is the professional choice: multi-node, dozens of games, billing integrations, and a setup that takes an afternoon and rewards it with the widest ecosystem. Crafty Controller is Minecraft-only like Lodestone in practice, Python rather than Rust, with scheduled backups and a very active Discord; it is the closest direct competitor and the safer pick if you want frequent releases. PufferPanel sits between: a single Go binary with a decent game template library and less polish.

Lodestone wins when you want the lightest install, the desktop-app option, and macros. It loses on game breadth and release cadence. There is no configuration in which it beats Pterodactyl for a public multi-game community.

What I'd do

For a home Minecraft setup on a mini PC or an old laptop, install the Lodestone container with the data directory on real storage, create the owner account, spin up a Paper instance with 4 GB allocated, and write one macro for a nightly restart and world backup. Keep the dashboard on the LAN or behind Tailscale. If your group later wants Valheim and Palworld too, that is the moment to migrate to Pterodactyl, and the world folders move over unchanged. Until then, one binary is enough.