EpicWing a Self Hosted Server Management Panel

Self-hosted server management panel.

Run game servers and other services in isolated Docker containers.

Installation · Features · Documentation · Limitations · Changelog

EpicWing is a self-hosted server management panel. Game servers and other services each run in their own isolated Docker container on a node. The panel talks to a small Go agent on each node.

Status: beta. Fine for small setups, not ready for large or multi-tenant hosting. See Limitations.

Panel: a fresh Debian 13 (x86_64) server with a domain or an IP, ports 80 and 443 open

Node: Debian 13 (x86_64) with Docker already installed, and the enrollment token from the admin area

Everything else (PostgreSQL, nginx, TLS, the agent) is set up by the installer

Installation

Tested on Debian 13 (x86_64). On a fresh machine, as root:

bash <(curl -fsSL https://raw.githubusercontent.com/EpicWing/epicwing-panel/main/scripts/install.sh)

The script asks whether to install the panel or a node. The panel installer sets up PostgreSQL, nginx, TLS and the first administrator. For a node you need the enrollment token from the admin area, and Docker must already be installed. You can also name the target directly:

bash <(curl -fsSL https://raw.githubusercontent.com/EpicWing/epicwing-panel/main/scripts/install.sh) node --panel https://panel.example.com

Options, the manual installation, updating and troubleshooting are in docs/INSTALL.md.

Minecraft (Vanilla, Paper, Purpur, Fabric), Unturned and a static website. Pterodactyl-format egg files can be imported for everything else.

Panel backend: FastAPI (Python 3.13), PostgreSQL or MariaDB, Alembic migrations

Panel frontend: Vue 3, Vite, Tailwind

Agent: Go, runs on every node and controls Docker, files, backups and SFTP

Features

Users, roles, 2FA (TOTP), API keys and SSH keys

Nodes with Ed25519 agent authentication

Servers, nests and eggs (imports and exports Pterodactyl-format egg files)

Install, start, stop, restart, live console, auto restart

File manager with direct transfers, SFTP

Local backups, schedules, databases per server

Notifications through Discord and email

Traffic guard: detection of unusual incoming traffic and console floods with alerts

In-panel guide for administrators

Documentation

Installation, updating and troubleshooting

Architecture

Agent protocol

Installer security

Changelog

Contributing

Limitations

DDoS: EpicWing only detects and reports unusual traffic. It blocks nothing, so use your provider's protection or a firewall for that.

Tested on Debian 13 (x86_64) with systemd and Docker only.

The panel runs as a single process. Schedules, rate limits and action locks are kept in memory, so do not run several workers.

Backups are stored on the node. There is no S3 or cross-node storage yet.

No built-in web hosting features (domains, vhosts, TLS). A site or app can run as a container if you have an egg for it, but you set up the reverse proxy and certificates yourself.

Only the Minecraft EULA is handled. When a server stops because it is not accepted, the console offers a dialog that links the EULA and sets eula=true after a click. The panel does not record who accepted.

The agent needs access to the Docker socket, which is equivalent to root on the node. Run nodes on dedicated machines.

Development

See scripts/dev.sh for local work. Checks that CI runs:

Bug reports and pull requests are welcome, see CONTRIBUTING.md.

Support: support@epicwing.de

Abuse reports: abuse@epicwing.de

General questions and other inquiries: info@epicwing.de

Community: Discord server

Bugs and feature requests belong in the issue tracker.

See SECURITY.md to report a vulnerability.

MIT. EpicWing imports Pterodactyl-format egg files for compatibility. It is not affiliated with Pterodactyl. See docs/LICENSING_AND_ATTRIBUTION.md.