Terminology
Common Skyport terms used throughout the documentation.
The main web application. Handles authentication, administration, node management, server records, and the user-facing UI.
skyportd
Section titled “skyportd”The daemon that runs on each node machine. Enrolls with the panel, receives configuration, and manages Docker containers.
A machine capable of hosting server workloads. Each node has an FQDN, daemon port, SFTP port, and location assignment.
Location
Section titled “Location”A logical grouping for nodes, typically representing a region (e.g., Frankfurt, Ashburn, Singapore).
Allocation
Section titled “Allocation”A bind IP and port pair on a node. Each server claims one allocation as its primary address.
Server
Section titled “Server”A managed workload belonging to one user, one node, one allocation, and one cargo.
Skyport’s server definition package. Describes how a server is installed and started — startup command, install script, Docker images, variables, and stop behavior.
If you are coming from Pterodactyl, cargo is the equivalent of an egg.
Configuration token
Section titled “Configuration token”A one-time token generated by the panel to bootstrap skyportd enrollment on a node.
Daemon secret
Section titled “Daemon secret”The long-lived credential issued to an enrolled daemon for ongoing communication with the panel.
Octane
Section titled “Octane”Laravel Octane is the high-performance application server used by the panel, running on Swoole.
Swoole
Section titled “Swoole”The PHP extension and server backend used by Octane to keep the application in memory across requests.
Server-side rendering. The panel uses Inertia SSR to render React pages on the server before sending them to the browser, improving initial load performance and SEO.