Skip to content
Evodactyl

Wings

What Wings does

  • Runs game-server containers on a Linux host via the Docker API.
  • Exposes an SFTP server so end users can edit files inside their game-server volume.
  • Streams console output and resource stats to the panel over WebSocket.
  • Pulls per-server configuration from Evodactyl’s Remote API (/api/remote/*) and receives power / backup / file-management commands via short-lived JWTs signed by the panel.

What Wings is not

  • Not an HTTP panel. It has no UI.
  • Not a database. It stores only ephemeral per-server runtime state on disk.
  • Not Evodactyl. It is a separate Go binary maintained by a separate project with its own release cadence, issue tracker, and maintainers.

How the two fit together

    end user ─── HTTPS ───►  Evodactyl Panel  ◄── JWT (HTTP + WS) ───►  Wings daemon  ──►  Docker
    (browser)               (Bun/TS, this repo)                         (Go, upstream)       (game server
                                                                                              containers)

The panel issues JWTs signed with a per-node daemon token. Wings verifies the signature and acts on behalf of the requesting user (start a server, tail logs, stream a backup, etc). Wings does not touch the panel database directly — everything goes through /api/remote/*.

Pages in this section