Service terms

Creating an account provides access to the free base panel. It does not create a paid subscription, and no payment details are required. This website does not currently provide self-service checkout. Before paid access begins, Aperture and the customer agree a written order identifying the operator, customer, price, billing period, included support, service term, and any jurisdiction-specific terms. That order controls if it conflicts with this page.

Aperture provides a hosted management layer for game servers on a Linux machine the customer owns or rents. The customer supplies and remains responsible for that machine, its hosting agreement, network availability, game licenses, and the content operated on it. Player TCP and UDP traffic uses Aperture’s relay to reach the assigned game address; game processes and files remain on the customer’s machine.

Early-access features may change and maintenance may occasionally interrupt the control plane. Aperture will use reasonable care, communicate material planned changes, and provide the support stated in the written order. No uptime commitment or service credit applies unless that order expressly includes one.

Customers must keep credentials secure, provide access only to authorized users, keep their machine reasonably patched, and report suspected compromise promptly. Aperture may restrict access needed to contain a security incident or a material acceptable-use breach.

The panel’s current Local game backups are stored on the connected machine. They do not protect against loss of that machine. Keep a separate copy of important game files and worlds elsewhere. Aperture keeps private disaster-recovery snapshots of hosted account, panel and control-plane state. These snapshots do not include the customer’s game files. Managed off-site game-backup storage is not currently included.

Each customer account may own one workspace at a time, including a reserved, setting-up or inactive workspace. A workspace can contain multiple machines and game servers. Creating extra accounts to evade limits or installation rate controls is not permitted.

A new name is reserved for seven days. The hosted workspace starts when the machine installer is actually used; email confirmation is required before connecting the first machine. Unfinished installation attempts also expire.

A workspace becomes inactive after 31 days without any authenticated, reachable Wings node. A working node counts even when all game servers are stopped. Account visits and Resume clicks alone do not reset inactivity. Aperture monitoring outages or incomplete observations must not be treated as proof of customer inactivity.

Aperture retains the inactive workspace’s hosted configuration and name for a further 365 days after it becomes inactive. Resume and reconnect a working node before the deadline shown in your account to keep the workspace. After that recovery period, the hosted workspace configuration is permanently removed. Names may become available to a new owner only after cleanup and quarantine; the former tenant identity and data are never transferred.

Game files on customer machines are left untouched. Their presence does not restore deleted panel settings, user records or server-management metadata. Keep independent exports and game backups. Aperture shows deadlines in the account workspace and sends warnings before suspension and permanent removal. Existing workspaces receive a fresh grace period when this policy is introduced.

Cancellation, renewal, payment, refund, data-export, and deletion timing are set in the written order. A customer should request any needed export before access ends. For service or contract questions, contact hello@aperture.sh.