Skip to content
Spirit Panel Self-hosted
Spirit Panel — Manage, Host, Grow

Self-hosted · AGPL-3.0

The game server panel you host yourself.

A web UI for users, nodes, and servers. Games stay in Docker on FeatherWings, on this machine or on their own nodes.

Get started See features
FeatherWings
Docker for every server
One panel
Local daemon and remote nodes
AGPL-3.0
You get the whole panel

Spirit Panel

Game server hosting

My servers

play.example.com:30120

Ping 42 ms

Uptime 19m

Players 0

US-NYC

Notice What are your thoughts on Spirit-Panel?

We're always working to improve Spirit Panel. Have feedback or suggestions? We'd love to hear from you.

Rogue Network Roleplay / Console Running

Installation in progress

Reconnect

CPU 9.4% RAM 533.9 MB DISK 1.98 GB NET ↓ 128.3 KB/s ↑ 59.4 KB/s

[script:cc-chat] =============

[script:cc-chat] CC Chat (cc-chat) is outdated!

[script:cc-chat] Current version: (v1.4.2)

[script:cc-chat] Latest version: (v1.4.1) github.com/example/cc-chat/releases/tag/v1.4.1

[script:cc-chat] There is a known issue with version checks. When the check fails, a specific error is shown instead of a generic one.

[script:cc-chat] =============

[resources] Started map fivem-map-skater

[resources] Started resource fivem-map-starter

[script:Badger_Discord] [Discord API] Script Working.

[script:Badger_Discord] [System] READY!

[script:spirit-notify] [Spirit Notify] Checking for updates…

[script:spirit-duty] [Spirit Duty] Ready. 4 departments on file.

[script:spirit-vehicle] [Spirit Garages] Ready. 2 owner(s) on file.

[script:spirit-safes] [Spirit Safes] Checking for updates…

[script:spirit-spawn] [Spirit Spawn] Checking for updates…

[script:spirit-notify] [Spirit Notify] Update check finished. HTTP status: 0

[script:Badger_Discord] Badger_Discord_API is up to date!

[script:DiscordAcePerms] DiscordAcePerms is up to date!

[script:spirit-safes] Update check failed. HTTP status: 0

[script:spirit-spawn] Update check failed. HTTP status: 0

[citizen-server] Server list metadata is now managed in the server portal. Leave name, tags, and banner blank here if you set them there.

[citizen-server] Your server name, description, tags, and banner images are managed from the panel.

[script:Badssentials] Badssentials is outdated. Current version: 3.2.1

[script:Badssentials] Latest version: 3.8.0

Commands unavailable during installation

Nests and eggs

Pterodactyl eggs, grouped into nests.

Bring the egg JSON you already use. A nest is the category. The egg is the template FeatherWings uses to start the server.

01 · Nest

A category you name

  • Related eggs, one place
  • A name you choose
  • As many eggs as you need

02 · Egg

PTDL_v2

egg-export.json

  • docker_images
  • startup
  • variables
  • installation

A newer import refreshes the template and keeps the servers already on it.

03 · Server

Docker on FeatherWings

  • Console
  • Files
  • Backups
  • Schedules

The panel never runs the game itself.

Minecraft plugins from Modrinth and the FiveM marketplace ship with the panel. Other games come from the eggs you import.

Same box or remote

Built for the machine you already have.

The panel is the control plane. FeatherWings, with Docker, is what actually starts each game. One panel can use a daemon on the same host and nodes on other machines at the same time.

Spirit Panel

Users, nodes, and servers

Control plane

The web UI, sessions, and API live here. The game process does not.

Same box

Daemon on this host

127.0.0.1:8080

nginx proxies the console websocket at /wings/.

Remote node

Daemon on another machine

API_URL

HTTPS, no trailing slash. It must match the FeatherWings remote exactly.

On the node

Every server in its own container

  • FeatherWings starts the container
  • CPU, RAM, disk, IO, and swap
  • A limit of 0 means unlimited
  • Reconnect on FeatherWings 1.4.3+

For players

The client area

  • Console with tab completion
  • Files, editor, and startup
  • Power, backups, and databases
  • Schedules, subusers, SFTP, tickets

At sign-in

Sessions and keys

  • HttpOnly session cookies
  • Optional 2FA
  • Scoped application API keys
  • Checks before a production boot

Install

Install it on your own server.

Ubuntu 22.04+ or Debian 12+. Ubuntu 24.04 LTS is the recommended production host.

  1. 01

    Point DNS first. The domain has to reach the server before the certificate is issued.

  2. 02

    The script provisions the stack. Node 20, pnpm, MariaDB, Redis, nginx, and Let's Encrypt.

  3. 03

    Save the script, then run it. Do not pipe curl into bash under sudo.

Install steps Read the docs

Two commands

The menu covers install, update, status, backup, and uninstall.

spirit.sh

curl -fsSL https://raw.githubusercontent.com/SpiritFramework/SpiritPanel/main/scripts/spirit.sh -o /tmp/spirit.sh

sudo bash /tmp/spirit.sh 

curl -fsSL https://raw.githubusercontent.com/SpiritFramework/SpiritPanel/main/scripts/spirit.sh -o /tmp/spirit.sh
sudo bash /tmp/spirit.sh

License · AGPL-3.0

The panel you install is the whole panel.

SpiritFramework/SpiritPanel GitHub

01

Source

The files on GitHub are the panel you install.

02

Issues

Bugs and changes are tracked on the same repository.

03

Releases

Published versions stay next to the source they came from.

Network service. If you change Spirit Panel and run that version as a network service, you offer the corresponding source to the people using it.