🌳

Documentation

Everything you need to run Yggdrasil Panel — from a bare Debian box to a fleet of game servers, backups and all.

Getting started

From a bare Debian box to a running game server.

Lifecycle, console, files, cloning, tags, bulk actions.

The catalog: what ships, and how to add more.

Measure the image first, then let a model write the YAML.

Targets, restore, verification, retention, cron.

Move a whole panel to another machine — bundle or rsync.

Ports, reachability, UniFi, NPM, Cloudflare Tunnel.

Metrics, alarms, the watchdog, auto-restart.

Telegram, Discord, webhooks — and what triggers them.

Realms, permission bits, delegates, 2FA, tokens.

The public board, the Discord embed, and the beacon you can switch off.

The optional AI assistant and its safety model.

Let Claude read and drive the panel over MCP.

Lifetimes, globals, mod loot, surviving a reinstall.

For integrating with a panel or writing your own runes. The deep reference lives on GitHub, next to the code it describes.

Every key in config.yaml.

Every route, its auth, and its permission gate.

The YAML format for teaching Yggdrasil a new game.