Today we’re proud to announce the stable release of Craftbox 1.0 — our self-hosted web panel for creating, configuring, and managing Minecraft servers without ever touching a command line.
After two and a half months of development, 32 public beta versions, and a lot of late nights staring at server logs, Craftbox has officially shed its beta tag. It’s now ready to be your daily-driver Minecraft server management solution.
The road to 1.0, in numbers
Hundreds of hours were spent planning, building, iterating, testing, and playing went into Craftbox’s development. Here’s what went down:
- 32 beta versions shipped, with 30 of those being public.
- 12+ headline features added during the beta period.
- 40+ documented bug fixes, quality-of-life tweaks, and stability improvements.
A personal note from WillTDA (Founder of Diamond Digital Development)
"For the entire beta period, I ran Craftbox on an ARM-based VPS to host a heavily modded Java SMP. I wanted to design Craftbox to handle as many edge cases and essential management tasks as possible, so about 10 of my friends and I got together to build a huge modpack — and nobody was allowed to know what mods anyone else had suggested. The idea was that we’d end up with a massive pile of major, game-changing mods that would push the server’s stability to its absolute limit. (That’s exactly what ended up happening, by the way.)
Sure, I had my initial design document, but doing this turned up so many bugs, UI tweaks, new feature ideas, and quality-of-life improvements that turned multi-minute jobs (if you knew exactly what you were doing) into a couple of clicks in the browser.
When hosting Minecraft servers with my friends in the past, I’d always find myself needing to step in to fix something — manually starting it back up after a crash, jumping in to run slash commands, creating backups before big changes, rolling things back when they went sideways, adding new mods to the pack. The list goes on. I had it in mind from the very beginning to make the app properly responsive, too, so I could remote-control my servers from my phone while out and about.
To sum it up: Craftbox is the result of taking every frustration I’ve ever had with hosting Minecraft servers and making the whole thing so easy that anyone can do it."
The Craftbox API
The single biggest addition to land during beta was the dedicated Craftbox API. Up until then, Craftbox was very much a “use it through the browser” experience. Now, you can build your own integrations on top of it.
Some of what landed alongside the API:
- API key management in account settings — generate keys, name them for easier organisation, and revoke them whenever you need to.
- A
POST /api/v1/servers/:id/commandendpoint for running commands on a running Minecraft server programmatically. - A full internal refactor of the Craftbox codebase to use the new unified API architecture under the hood.
This is groundwork for a lot of cool things going forward — Discord bots that can restart your server with a slash command, custom dashboards, scheduled automations, and whatever else the community can dream up.
New features that landed during beta
Plenty of features made their way in over the course of the beta period. Some highlights:
- Custom server icons and an in-browser MOTD creation tool — your servers can now look exactly the way you want in the multiplayer list, without needing to fiddle with files manually.
- Mod environment selectors — when managing a modpack, tell Craftbox whether each mod is client-side, server-side, or both. The server only loads what it needs, and the downloadable modpack only includes what players need.
- Background server deletion — large server deletions used to block the UI. Now you’re redirected back to the dashboard immediately and the deletion happens in the background.
- In-progress overlays for long-running operations like provisioning, backups, and server duplication, so you always know what’s happening.
- Support for Minecraft’s new “game drop” versioning (26.1 and beyond) so Craftbox keeps pace with the latest Minecraft releases.
- Advertised IP option for public status pages — the IP your players use to connect can now differ from the one Craftbox sees internally.
- OpenGraph metadata on every page, so links to your status pages embed nicely in Discord and elsewhere.
- Live WebSocket updates across every server management sub-page — settings, properties, plugins, files, backups, and events. No more 30-second auto-refreshes.
Stability and security improvements
A lot of the work during beta wasn’t flashy — it was the unglamorous business of making sure Craftbox behaves itself in production. Some of the more notable fixes and hardening efforts:
- Zombie process reaping in Docker. JVM descendants like Forge/NeoForge installer sub-processes weren’t being properly reaped, which would slowly exhaust the host’s PID limit over time. We now spawn JVMs as POSIX process-group leaders and run
tinias PID 1 in the Docker image to make sure nothing gets left behind. - Stronger JAR validation. Uploaded JARs are now checked to ensure their first bytes follow the conventions of a zip archive, and checksums are verified before executing server JARs.
- Symlink protection for mods. Malicious mods can no longer use symlinks to access restricted files like the Craftbox database.
- Username enumeration protection. Authentication failures now perform a dummy hash to prevent attackers from inferring valid usernames by measuring response times.
- No more ambiguous server states if Craftbox restarts mid-operation.
- Dedicated
BACKING_UPandRESTORINGstates so servers can’t end up in a contradictory state during backup operations. - Live resource monitoring for all running servers, polled every 10 seconds and retained for up to 5 minutes.
- Backup scheduler persistence fixes — scheduled backup times are now stored in the database rather than memory, so they survive a Craftbox restart.
There were dozens more — old Minecraft versions getting stuck in STARTING, crash banners disappearing in the live console, MOTD previews not saving correctly, join/leave regexes choking on rank prefixes — but the short version is that Craftbox is dramatically more robust than it was at beta.3.
Craftbox is fully open source and free to use, and it’s going to stay that way. If our software is useful to you, please consider buying us a coffee — donations are how this stuff keeps moving forward. We’d also appreciate any feedback you may have about Craftbox, whether it’s a new feature suggestion or a bug that needs addressing.
- Join our Discord Server
- Found a bug? Open an issue
- Have a suggestion? Submit a feature request
Here’s to 1.0.
- WillTDA, Founder of Diamond Digital Development