Yes — all three apps are free and open source. There's no license key, no paid tier, and no telemetry phoning home anywhere. You're running the code on your own hardware.

No. The Installer runs every Docker/apt command for you, and Server Manager handles updates the same way. The only Linux skill involved is pasting one command over SSH to kick off the install — everything after that is a browser. See Prerequisites for the full breakdown of what is and isn't required.

Yes. Crafty itself supports multiple servers on one machine, and both Mod Manager and Server Manager are built around managing several at once — the Fleet Overview in Server Manager lists every server you're tracking with its version, mod count, and pending updates at a glance.

The Installer and Server Manager both run as root and are gated by an access token generated at install time — treat that token like a password. All three dashboards are meant to stay on your local network; none of them should be port-forwarded to the public internet. Mod Manager has no token by design since it only ever touches mod/plugin files, not system-level commands.

Yes, but that's a separate step from anything Anvil does — you'd forward the Minecraft port (25565 by default) on your router to your server's local IP. The Anvil dashboards themselves should never be exposed this way; only the Minecraft server port itself.

Every step in the Installer is independent and safe to re-run — if Docker installation fails because of a network blip, just click it again once the issue's resolved. Nothing moves on to the next step automatically, so you always know exactly what has and hasn't run.

Anvil Server Manager uses restic under the hood — a well-established, encrypted, incremental backup tool. You point it at a local path (ideally a second disk) or an S3-compatible/Backblaze B2 bucket, and it can run on a schedule you set. Restoring always writes to a fresh staging folder rather than overwriting a live world, so a restore can never accidentally clobber something you didn't mean to touch.

Yes — the Installer has a Danger Zone with a per-component uninstall for Docker, Crafty, Cockpit, Mod Manager, and Server Manager, plus a self-destruct option for the Installer itself. Deleting Crafty's actual world data is a separate, explicit checkbox that only unlocks after you've downloaded a backup — it won't happen by accident.

Crafty Controller itself supports Bedrock servers, and the Installer opens the Bedrock port as part of firewall setup. Mod Manager is currently focused on Java Edition mods/plugins/datapacks (Modrinth and CurseForge), since Bedrock's add-on ecosystem works quite differently.

It's saved on the server itself: /etc/anvil-installer/token for the Installer, and /etc/anvil-server-manager/token for Server Manager. SSH in and run cat on the relevant file to see it again.

No. Anvil MC is an independent, community project. Minecraft is a trademark of Mojang/Microsoft, and Crafty Controller is its own separate open-source project that Anvil builds around, not a part of.

Each app has its own GitHub repository — open an issue on whichever one it concerns. Links are in the footer of every page, or on the Download page.