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
These public docs focus on the platform buyer: hosting-business architecture, Content YAML authoring, deployment boundaries, and supportable operations.
Provider authoring
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.
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 referenceReview how ordering, control-plane policy, the Container Engine Agent, and managed hosts fit together.
Provider platformSee how a retail provider implementation can be discussed without making this site a retail hosting store.
View exampleAuthoring workflow
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.
Only validated files placed in catalog/products/ are runtime catalog products. Templates and examples are validatable authoring aids, not customer-visible catalog entries.