VulCode

Pterodactyl: setup, theming and billing integration

We set up the panel and Wings nodes, configure eggs for your plans and connect Pterodactyl to your store or billing system. A game server appears once the order is paid and goes away when the service expires. We also say plainly when our Flaem panel fits better.

Hosting companies
A Minecraft server order in the integration panel: the service status, Application API calls with a retry after no reply and the body of the POST /api/application/servers request

We know this kind of panel from the inside

Our plugin update fix was merged into Pelican, an actively developed Pterodactyl fork, as described in our tech news. We also build Flaem, our own panel for hosting companies, so we know where game hosting automation usually breaks.

The WaveHost client panel with balance, services and invoices

WaveHost: the client panel

The WaveHost client panel: ordering services, wallet, invoices, referrals and an account linked to the game panel through an HMAC handshake.

See: WaveHost: the client panel
Panels in our portfolio

What Pterodactyl is made of

The panel and the nodes are separate installs. Each one is set up and maintained differently.

paid orderorders to the panela server to installinstall from a template
Store or billing
e.g. WHMCS
Operation queue
our integration
Pterodactyl panel
accounts, plans and servers
Wings on a KVM node
runs the game servers
Game server
installed from a ready template

Allocations

  • An IP and port pair

    An allocation is an IP and port pair. Every server needs at least one.

  • Named or picked by the panel

    The integration can name an allocation directly or let the panel pick one through automatic deployment in a location.

The service lifecycle in the integration

Paid, installing, active, suspended, removed: each status starts its own operation in the panel. The queue sends them at a pace the panel accepts.

The integration's operation queue: a chart of night suspensions for missed payments under the panel limit of 256 requests a minute, today's operations with their calls and the service lifecycle rules
  • activesuspended

    Bulk suspensions at the panel's pace

    Bulk operations, such as suspending many services at once, go through a queue to stay under 256 requests per minute. If the panel refuses, the operation goes back to the queue.

  • activesuspendedremoved

    Suspension, then removal

    Suspension after a missed payment, resumption right after payment and removal after a grace period you choose. It all happens on its own, with no manual work by support.

  • active

    A plan change on the same server

    Plan change: more memory, CPU or disk. Reinstall: on the customer's request, after confirmation.

What a billing system asks the panel to do

The operations in the order a service reaches for them: from the first purchase to removal.

  • Store or billinge.g. WHMCS
  • Operation queueour integration
  • Pterodactyl panelaccounts and servers
  • Wingson a KVM node
  1. Store or billingOperation queue

    Step 1 of 8: paid order

  2. Operation queuePterodactyl panel

    Step 2 of 8: Player account

    First purchase, tied to the customer's store account

  3. Operation queuePterodactyl panel

    Step 3 of 8: Create server

    After the order is paid

  4. Pterodactyl panelWings

    Step 4 of 8: install from a template (in the background)

    The panel created the server, and Wings installs it from the game template.

  5. Operation queuePterodactyl panel

    Step 5 of 8: Plan change

    More memory, CPU or disk

  6. Operation queuePterodactyl panel

    Step 6 of 8: Suspend and resume

    Missed payment and payment

  7. Operation queuePterodactyl panel

    Step 7 of 8: Reinstall

    On the customer's request, after confirmation

  8. Operation queuePterodactyl panel

    Step 8 of 8: Removal

    After the grace period

What the hosting customer sees

The client panel shows the service status from the integration and what the customer can do about it, without writing to support.

A hosting client panel on a phone: a Minecraft server suspended for a missed payment with its removal date and a pay button, and a running SCP:SL server with a change plan button

  • Server suspended, files in place

    The customer sees since when the server has been stopped and when it goes if the invoice stays unpaid.

    Suspended: The server is stopped after a missed payment. The data stays on the node.

  • A payment brings the server back

    Paying the overdue invoice resumes the server; no one in support has to switch it on.

    Suspended → active: Resumed right after the payment. The data waited on the node.

  • A bigger plan on the running server

    The customer changes the plan from the panel, and the server stays the same.

    Active: The server runs. A plan change raises its limits without creating a new server.

Common questions about Pterodactyl

Answers about Pelican, theming, key permissions, Flaem and the quote.

How many servers do you set up by hand today?

Tell us which panel you run and where customers buy services. We will reply within an hour with questions and a quote.