Skip to content

How Raptor works

Raptor has two halves: the Panel, the website you manage everything from, and Wings, the program that runs on your own machine and does the actual work.

You (browser) app.raptorpanel.net Your machine (a node)
│ │ │
│ click "Start" │ │
│─────────────────────────►│ a signed command │
│ │────────────────────────────────►│ Wings starts the
│ │ │ server in Docker
│ live console, stats ◄───│◄────────────────────────────────│
│ │ │
Players connect straight to your machine ◄──

The Panel is hosted by Raptor at app.raptorpanel.net. It’s where you:

  • create and manage servers: console, files, add-ons, backups, schedules, settings;
  • invite your team and decide what each person may do;
  • get alerts when something goes wrong;
  • pay for your plan.

There’s nothing to install or keep updated: Raptor runs it.

Wings runs on every machine you link, which Raptor calls a node. It:

  • runs each game server in Docker, kept apart from the others, with the memory, CPU, and disk limits you set;
  • restarts servers that crash, runs your schedules, and takes your backups;
  • serves your files to the file manager and over SFTP;
  • keeps its own records of everything, in a database on the machine.

Wings connects out to the Panel over an encrypted connection. You don’t open a port for Raptor, and the Panel never logs in to your machine.

The Panel Wings, on your machine
Your server files Never stores them Keeps them, and serves them
Running servers Asks for changes Runs them, restarts crashes
Schedules and backups Shows and edits them Runs them, on its own clock
Alerts Sends them to you Reports what happened
Dangerous actions Passes your signed request on Checks your passkey’s signature itself

Your servers keep running, and players don’t notice. Wings carries on with schedules, backups, and crash restarts on its own, and catches the Panel up when it’s back. Meanwhile you can still manage the machine from its own command line:

Terminal window
sudo raptor ps # every server and what it's using
sudo raptor restart survival # power actions
sudo raptor console survival # the live console

See the command line reference.

Its servers stop with it, and the Panel shows the node as offline, under Needs attention on the org’s home page too. You can still see its servers and settings, as they were last reported, but nothing can be changed until it’s back. When it reconnects, Wings starts the servers that were running and tells the Panel what happened while it was away.

Some actions can destroy data or change what code runs: deleting a server, restoring a backup over it, wiping it, changing its game or startup command, trusting a new person’s passkey. For those, the app asks your passkey to sign the exact request, and Wings checks the signature itself. So even someone who took over Raptor’s servers couldn’t do them without you. More in How Raptor protects you.

  • Org: your team, with its members, nodes, and servers. Billing is per org.
  • Node: a machine you’ve linked. It has a name, and an address like 1cdd002cd9a3.raptornodes.net that follows its IP.
  • Server: one game (or bot, or app) running on a node.
  • Egg: the recipe a server is made from: what it runs, how to install it, its settings. Raptor has a library of more than 350, and reads Pterodactyl eggs.
  • Short ID: the end of a server’s or node’s ID, shown in the app’s addresses and by raptor ps.

© 2026 Xena Studios. Pterodactyl is a trademark of its owners; Raptor isn't affiliated with it.