Content YAML authoring
Use the schema reference, canonical template, validation command, and safe public examples to add trusted game or application content without editing website, PHP, or JavaScript code.
Open referenceDocumentation
Run servers, publish trusted content, and keep platform boundaries clear.
These public docs cover the current Game Server Engine customer model and the provider-owned Content YAML format used by Containment Engine catalog entries.
Provider authoring
Content YAML is the catalog source of truth.
Providers can author one validated YAML file for an application or game. Active catalog entries become eligible for order cards, and lifecycle-backed entries also become eligible for Server Content.
Game hosting model
Customers rent private resource-based containers first, then install supported games through Server Content.
How hosting worksProvider platform
Containment Engine owns ordering, deployment, trusted Server Content, operations, alerts, support, and optional hosted services.
Provider overviewAuthoring workflow
Copy, edit, validate, publish.
A normal catalog addition starts from the template, replaces sample IDs and lifecycle metadata, validates locally, then moves the file into the runtime catalog folder.
Runtime rule
Only validated files placed in catalog/products/ are runtime catalog products. Templates and examples are validatable authoring aids, not customer-visible catalog entries.