01overwing org create
Create your operator workspace
Your organization is the security and ownership boundary for staff, nodes, servers, storefront settings, and renter accounts.
✓ organization ready
overwing topology
Operator
Brand, staff, customers, servers
Overwing
Identity, desired state, durable jobs, audit
control path carries commands and bounded telemetry—not player traffic.
Rook
Authenticated daemon on your node
Game servers
Processes, files, ports, backups
$ overwing journey
From an empty account to a live customer server.
02overwing node enroll
Install Rook on your server
Generate a short-lived enrollment token, run one command on your Linux machine, and Rook connects outward to Overwing. No control-plane SSH access is required.
✓ node authenticated
03overwing storefront publish
Make the customer experience yours
Add your business name, logo, theme, support details, catalog, included subdomain, and—when ready—a verified custom domain.
✓ storefront online
04overwing customer invite
Invite renters into your panel
Every renter account belongs to exactly one operator. Invitations, passwords, sessions, resets, and server access stay inside that tenant boundary.
✓ customer invited
05overwing server deploy
Deploy from the catalog
Choose a supported game, set resources and launch options, then let Overwing issue a durable job. Rook installs, starts, observes, and reports the result.
✓ instance running
06overwing fleet watch
Operate everything from one place
Use live console access, files, backups, metrics, player tools, audit history, node health, and session revocation without managing each box by hand.
✓ fleet healthy
$ overwing trace deploy
What happens when you click deploy?
1 · Dashboard
Validates your organization, role, game settings, and node capacity.
2 · Control plane
Records desired state and creates an idempotent, leased job.
3 · Rook
Claims the job, installs or updates safely, and starts the workload.
4 · Reconcile
Reports observed state, health, progress, and any actionable failure.
If a request is retried, the durable job model prevents duplicate servers and ports. Already-running games keep running through a temporary control-plane interruption.
Operator
Runs the business
Owns the nodes, brand, catalog, staff permissions, renter relationships, support, and infrastructure decisions.
Renter
Manages their servers
Signs into the operator-branded panel to see assigned servers, status, console, files, backups, and game controls.
Player
Connects directly
Joins the game on the operator’s node. Gameplay traffic never detours through Overwing’s web control plane.
$ overwing trust
Designed around clear boundaries.
Overwing coordinates your fleet without pretending the web panel owns the hardware. Authority stays explicit at every layer.
- Tenant isolation
- Organization IDs travel with renter accounts, sessions, jobs, servers, and audit events; cross-tenant access is denied.
- Outbound node connection
- Rook calls outward to the control plane, so operators do not hand Overwing an SSH credential or expose a privileged management API.
- Hashed, revocable credentials
- Enrollment, invitation, reset, and session bearer values are single-use or revocable, with only hashes retained where applicable.
- Direct game traffic
- Players connect to the node that runs the game. Overwing carries control messages and bounded operational data, not the gameplay data path.
Bring your own node
Ready to put your first machine under one panel?
Start with one operator workspace and one node. The same model grows to more renters, games, servers, staff, and hardware without changing how you operate.