Pterodactyl had a good run. Raptor does everything you run Pterodactyl for, with the add-ons built in and no panel to host: run one command on any Linux box, and manage it from the web.
Raptor is a hosted game server management platform. You bring your own Linux machine (a dedicated server, a VPS, a spare box at home), run a single install command, and it links to the web panel at raptorpanel.net. From there you create and manage game servers, Discord bots, and voice servers.
Raptor is compatible with Pterodactyl and Pelican eggs, and raptor import pterodactyl moves existing servers over on the same machine. How the two compare, with prices: Raptor vs Pterodactyl.
Status: built and running in production ahead of launch, with no uptime promise yet. Wings (the daemon) runs servers from Pterodactyl and Pelican eggs with a full lifecycle, kernel-enforced disk limits, passkey-signed dangerous actions, schedules, encrypted incremental backups, SFTP, self-updates that roll back, and a local CLI and TUI. The Panel runs at raptorpanel.net with the web app, billing, and a standby server streaming from the first. What's left before launch (the failover and billing drills, the beta, the soak test) is in the roadmap.
| Component | What it is | Where it runs |
|---|---|---|
| Panel | Web app + API. Users, orgs, auth, billing, node enrollment. | Raptor's infrastructure (SaaS only) |
| Wings | The daemon. Runs servers in Docker, schedules, backups, SFTP, crash recovery. Keeps working when the Panel is unreachable. | The owner's Linux box |
raptor CLI |
Local tool for keeping servers up: status, power, console, logs, backups and restores, doctor. |
The owner's Linux box |
Running Raptor? The guides are at docs.raptorpanel.net (docs-site/), and help is on Discord. The documents below are for contributors: how Raptor is built, and why.
- Product outline: what Raptor is and who it's for
- Architecture: how the pieces fit together
- Wings: the daemon in detail
- Panel: the SaaS control plane
- Design: the web app's design system
- Deploying: running the Panel's servers
- Servers: server model, states, ports, console, crash policy, deletion
- Egg compatibility: Pterodactyl/Pelican egg support
- Security model: threat model and security rules
- Reliability and performance: requirements and how we meet them
- Decisions log: every locked decision and why
- Roadmap
Raptor is licensed under the GNU Affero General Public License v3.0. Contributions are accepted under the Developer Certificate of Origin.
