Aerie is one open-source app to sell, bill and run game servers. It drives the Wings and Elytra nodes you already have, so switching never stops a game.
AGPL-3.0. Self-hosted. In development, not yet released.
Follow one Server through a month. Your Staff panel and your Client's panel are two views of the same record, so a payment, a missed renewal or a migration changes both at once. This is how v1 is designed to behave.
Mara picks MC 8 GB in US Central and pays through Stripe. That payment is what creates the Server, on the least-loaded Node in the Location. No module polls a second panel, because there is no second panel.
26 Sep 21:02
The card on file is declined. Both panels read the same unpaid Invoice: Staff see the row turn red, Mara sees a Pay button. The game keeps running through the grace days you set on the Plan.
26 Oct 00:00
When grace runs out, Aerie tells the Daemon to stop the Server and stamps it Suspended. Files stay on the Node. Termination waits for the second window you configured, and Staff can exempt a Client at any point.
29 Oct 00:00
Mara pays. The same record flips back: the stamp lifts, the Daemon starts the Server, and the paid-through date moves on. Nobody on your team touched it.
30 Oct 18:41
Now picture that Server on your current stack. The importer reads your panel and billing databases, shows you a dry run, then repoints the Wings or Elytra Daemon at Aerie. The Server stays Live the whole time and its Subscription arrives with it.
Cutover night
| Server | Client | State | Paid through |
|---|---|---|---|
| play.embercraft.ggMC 8 GB · ord-03 · paid to 26 Oct | Mara Okafor | Live | 26 Oct |
| vh.northhold.netPool 24 GB · ams-01 | Northhold Guild | Live | 02 Nov |
| ark.fernbank.ioARK 16 GB · ams-02 | Priya Nair | Stopped | 14 Nov |
26 Sep 21:02 INV-0142 paid. Server created on ord-03.
Powered by Aerie
Sample data. One record, read by both panels.
Your Nodes already run Wings or Elytra. Aerie v1 is designed to speak their API, so moving over is a database import and a config change on each Daemon, not a reinstall.
| Nodes | 4 | ord-01, ord-02, ord-03, ams-01 |
|---|---|---|
| Eggs | 37 | PTDL_v2, imported as they are |
| Servers | 312 | 302 running, 10 stopped |
| Clients | 241 | with sign-in and 2FA settings |
| Subscriptions | 287 | matched to Servers by service ID |
| Unmatched | 3 | listed for you to resolve first |
Point the importer at your panel database and your Paymenter or WHMCS database. It reads, writes nothing, and prints what it would bring over, including anything it can't match.
Nodes, Eggs, Clients, Servers, Plans, active Subscriptions and open Invoices land in Aerie as one record per Server. Your old panel keeps running untouched.
Each Wings or Elytra Daemon gets Aerie's URL and token. The game processes are left running, so players stay connected while the panel underneath them changes.
Everything below lives in one codebase and one database. No billing module, no sync plugin, no second login for your Clients.
Aerie is free software. Run it, change it, host it for your Clients. If you offer a modified Aerie to others, you share your changes too.