Administration
Applications, games, and operations
Use the panel’s workload areas to create, deploy, observe, and recover the workloads supported by Forge.
#Applications
The admin routes include applications, Dockerfile and image deployments, Compose stacks, Git providers, Git sources, deployment history, revisions, previews, domains, certificates, DNS providers, and application templates. Use the Applications area for workload configuration, the Deployments area for execution history and revisions, and Domains for exposure.
A visible route is not a promise of a fully automated production workflow. Validate domain routing, Git webhooks, rollout strategy, and rollback in a non-critical environment before offering them as a service.
#Game servers
The admin routes cover servers, nests, eggs, startup variables, allocations, mounts, files, terminal access, backups, and cron jobs. A game server requires an eligible Beacon node and a network allocation. Test UDP allocation paths and firewall rules before publishing UDP-dependent games.
#Infrastructure
Nodes, regions, locations, scheduler, autoscaler, traffic, load balancer, failover, health, monitoring, logs, Docker, host files, and host terminal are administrative capabilities. Host terminal and Docker administration cross a high-privilege boundary; restrict them to trusted operators.
#Operations and recovery
Use operations and activity history to inspect long-running work. Migration, evacuation, recovery, and failover screens require capacity, a healthy destination node, and shared backup access for stateful recovery. They are not a substitute for a tested disaster-recovery runbook.