Panelra vs Pterodactyl for Rust Servers

Pterodactyl is one of the best known open source game panels, and a lot of Rust admins end up there because it is free. This page is an honest look at where it is stronger than Panelra, where Panelra saves you work, and who should not switch. Everything about Pterodactyl below comes from its documentation and source code as of 2026-09-28.

What Pterodactyl is

Pterodactyl describes itself as "the open-source game server management panel built with PHP, React, and Go" (pterodactyl.io). It has two parts:

• The Panel is the web app. It needs PHP 8.2 or 8.3, MySQL or MariaDB, Redis, a web server such as NGINX and Composer. It is supported on Ubuntu 22.04 and 24.04, Debian 11 to 13 and RHEL, Rocky and AlmaLinux 8 and 9.
• Wings is the daemon on each game machine. It runs every game server in an isolated Docker container and does not run on Windows.

Games are defined by "eggs". The stock Rust egg installs the server with SteamCMD (app 258550) and starts it with a command line built from panel variables such as server name, world size, seed, max players and ports.

The Pterodactyl docs are direct about the effort involved: the panel "is a highly complex system requiring multiple dependencies and administrators willing to spend some time learning how to use it."

What Pterodactyl does better

It is free and open source. Panel and Wings are MIT licensed and actively maintained; the latest Panel release when we checked was v1.15.1 from 2026-08-14. You can read every line, patch it and run it without an account with anyone. Panelra's dashboard is a hosted service you depend on.

Many games from one panel. If your community runs Rust next to Minecraft or other games, Pterodactyl manages all of them in one place. Panelra is Rust only.

Container isolation. Each server runs in its own Docker container, so one game server cannot see another's files. Panelra runs Rust servers as systemd services directly on the host, as root.

File manager and SFTP. Pterodactyl has a browser file manager and SFTP access, both covered by per-user permissions. Panelra has a plugin config editor but no general file manager or SFTP, so for arbitrary file edits you still use SSH.

Very granular subuser permissions. Subusers get individual permissions for console, power actions, files, SFTP, backups, allocations, startup variables, databases, schedules and settings. Panelra has five fixed roles instead: Owner, Admin, Operator, Moderator and Viewer.

Generic schedules. A schedule runs on a cron expression and can send a console command, run a power action (start, stop, restart, kill) or create a backup, with a delay between tasks. That covers restart warnings and timed backups for any game.

Backups to S3. Backups are stored by Wings on the node or in S3-compatible storage, set with APP_BACKUP_DRIVER=wings or APP_BACKUP_DRIVER=s3.

Wider OS and CPU support. Wings runs on Ubuntu 20.04 to 24.04, Debian 11 to 13 and RHEL-family 8 and 9, and ships x86_64 and arm64 builds. The Panelra agent needs Ubuntu or Debian on x86_64 with systemd.

What Panelra does that Pterodactyl does not

Nothing to host except Rust. The Panelra dashboard runs at app.panelra.io. On your machine you run one install command, and the agent connects out to the dashboard over HTTPS on port 443, so there is no web server, database or Redis to maintain and no panel port to expose.

Real wipes on a schedule. Panelra wipes by deleting the map, and optionally the blueprint, files on the host: weekly, monthly, on specific dates, on Facepunch forced wipe days or right now. You can keep the seed, roll a random one, set a custom seed or use a custom map URL. The agent never writes a seed of 0 or below to server.cfg, because Rust treats 0 as "pick a new random map on every start". With the stock Pterodactyl egg a wipe means deleting files by hand or reinstalling with the community Autowipe egg.

Updates with a warning. The stock Rust image runs a SteamCMD update every time the container starts, so an update only happens when something restarts the server, and players are not warned unless you build that into a schedule. Panelra shows when the next auto-update will happen, can update now on request, and gives players a single 5-minute warning before the restart.

Crash alerts, not just restarts. Wings has crash detection: it restarts a crashed server unless the previous crash was less than 60 seconds ago, and prints the exit code and whether the container ran out of memory to the server console. We did not find crash notifications in the core Panel. Panelra detects crashes, crash loops, a server that stops responding, a server stuck while starting and a host or agent that goes offline, puts each in an alerts inbox and can post it to a Discord webhook. When a server dies from a SIGKILL, the agent checks the kernel log for an out-of-memory kill, so the alert itself tells you whether the machine ran out of RAM. Panelra does not alert on CPU or RAM usage.

Rust moderation built in. Web RCON console, player list, kick, ban, notes, F7 reports and broadcasts. A ban applies to every server in the team and is enforced when the player joins. The Moderator role can do all of that without being able to stop, wipe or reconfigure the server.

Plugins as a catalog. Pterodactyl's egg downloads the framework, and plugins go in through the file manager or SFTP. Panelra installs Oxide or Carbon in one click, installs plugins from the uMod catalog, edits their configs and can auto-update them. Removing a framework stops the server first and restores vanilla.

Setting each one up

Pterodactyl's Wings install on a game machine starts like this, after the Panel itself is installed and configured:

curl -sSL https://get.docker.com/ | CHANNEL=stable bash
sudo mkdir -p /etc/pterodactyl
curl -L -o /usr/local/bin/wings "https://github.com/pterodactyl/wings/releases/latest/download/wings_linux_$([[ "$(uname -m)" == "x86_64" ]] && echo "amd64" || echo "arm64")"
sudo chmod u+x /usr/local/bin/wings

The Rust egg then starts the server with a command built from variables. This is the start of it:

./RustDedicated -batchmode +server.port {{SERVER_PORT}} +server.queryport {{QUERY_PORT}} +server.identity "rust" +rcon.port {{RCON_PORT}} +rcon.web true

Panelra needs one command, run as root on the Linux machine. The dashboard shows it with a token for that host:

curl -sL https://app.panelra.io/install | sudo AGENT_TOKEN=<your-token> bash

After that you install Rust from the browser. The agent writes a systemd unit per server. This is the start command from a Carbon server on our Ubuntu 26.04.1 test host; carbon.sh sets up the doorstop preloader Carbon needs:

ExecStart=/opt/rust-servers/instance-1/carbon.sh \
    -batchmode \
    -nographics \
    +server.identity server-a7256791-5705-4c49-801a-a5044463dc38 \
    +server.port 28015 \
    +server.queryport 28017 \
    +app.port 28082 \
    +rcon.port 28016 \
    +rcon.web 1 \
    +rcon.password ${RCON_PASSWORD}
Restart=always
RestartSec=5

The RCON password comes from an environment file, so it does not appear in the unit.

Who should NOT use Panelra

Panelra is the wrong choice if:

• You run games other than Rust. Pterodactyl or another multi-game panel will serve you better.
• You want to self-host every component. Panelra's dashboard is a hosted service. If your rule is that nothing leaves your own infrastructure, Pterodactyl fits and Panelra does not.
• You need container isolation or SFTP for other people. Pterodactyl gives each server its own container and gives subusers SFTP. Panelra does neither.
• Your machine is ARM, Windows or a non-Debian distro. The agent needs Ubuntu or Debian (22.04, 24.04 or 12 recommended) on x86_64 with systemd.
• Your Pterodactyl setup already works. If your schedules, backups and wipes are sorted and someone on your team maintains the panel, switching buys you less.

Size the machine for Rust either way: plan for about 12 GB of RAM and 30 GB of disk per server. Players need 28015 and 28017 UDP open, Rust+ uses 28082 TCP, and RCON on 28016 should stay private.

Feature comparison

"Not verified" means we could not confirm it from Pterodactyl's docs or source either way. It is not a "no".

Pricing

How to try Panelra

Create an account at app.panelra.io, add a host and run the install command the dashboard shows you as root on your Linux machine. Once the agent connects, you can install Rust, pick Oxide or Carbon and set a wipe schedule from the browser.

Sources

Checked on 2026-09-28:

• Pterodactyl introduction: pterodactyl.io/project/introduction.html
• Panel requirements and supported OS: pterodactyl.io/panel/1.0/getting_started.html
• Wings install, supported OS and Docker: pterodactyl.io/wings/1.0/installing.html
• Backup drivers: pterodactyl.io/panel/1.0/additional_configuration.html
• Stock Rust egg: github.com/pterodactyl/panel egg-rust.json
• Rust container entrypoint (updates and Oxide or Carbon download): github.com/pterodactyl/yolks games/rust/entrypoint.sh
• Schedule task types: github.com/pterodactyl/panel app/Models/Task.php
• Subuser permissions: github.com/pterodactyl/panel app/Models/Permission.php
• Wings crash detection: github.com/pterodactyl/wings config/config.go
• Community Rust Autowipe egg: github.com/pterodactyl/game-eggs rust/rust_autowipe
• Latest Panel release: github.com/pterodactyl/panel/releases
• Panelra features: panelra.io/features