Provider platform
The control and operations layer for a hosting provider.
Game Server Engine / Containment Engine helps a provider move from order intake to isolated container deployment, trusted catalog content, support workflows, alerts, backups, and managed assistance.
O
Ordering and deployment
Convert provider-defined packages into repeatable container requests with controlled resources, ports, install defaults, and customer-visible options.
C
Server Content catalog
Trusted YAML records describe games or applications, variables, lifecycle actions, resource guidance, health checks, and optional price metadata.
P
Provider operations
Lifecycle control, logs, file access, alerts, backup/recovery boundaries, support escalation, and managed assistance stay in a provider-owned workflow.
Operational boundaries
Keep host authority behind the agent.
The panel remains the server-side control plane. The Container Engine Agent is the host-side privileged execution boundary, so customers interact with permitted service controls rather than raw host access.
Provider responsibilities
- Choose and publish retail packages for the provider's own market.
- Operate compatible endpoints or use optional hosted platform services.
- Define support, backup, recovery, and managed-assistance policy.
Game and application hosting
One provider platform, multiple catalog categories.
The same catalog and deployment model can support game-server hosting businesses and application-server hosting businesses. Providers decide which content categories they want to expose.
Game-server providers
Publish trusted game presets, mod guidance, port defaults, backups, and support workflows for gaming communities.
Application-server providers
Package private application environments with validated variables, ports, lifecycle commands, and endpoint policy.
Modernizing providers
Replace brittle manual provisioning with catalog-driven deployment and auditable operations.
Next step
Map your hosting operation to the platform.
Bring the expected host count, catalog categories, storefront needs, support model, and service endpoint preferences.