Most platforms call a page theme a template. Here a template is a versioned artifact with an author, a certification status, and a payload that installs into a working application. The four families do genuinely different jobs, which is why they are four things rather than four tags.
A complete application: modules, pages, layouts, menus, data connectors, bindings, user types, and theme. Install one and you have a working product to customize.
A single page, component, module, or data model added to an application you already have, without disturbing the rest of it.
A real service in its own container — document processing, a specialist model, an industry calculation — signed, versioned, and called like any other endpoint. Called appliance endpoints in the product.
Prompts, personas, glossaries, guardrails, and action sets for one industry, blocked from publishing until its evaluations pass. Called harness packs in the product.
Turn your brand direction into a consistent light or dark visual system that carries across application pages and registered components.
This is what separates an installable artifact from a screenshot with instructions attached.
Templates are versioned. You can see history, compare versions, and install the exact version you bought even after a newer one supersedes it.
Platform-authored, builder-authored, or partner-authored, with certification status shown. You know where it came from.
Not markup. A document describing modules, pages, components, bindings, actions, menus, user types, and theme variables.
Templates are validated before they can be listed, and a bad release can be revoked rather than chased down.
If you are not sure which blueprint fits, the documentation contains complete build guides that take a product you already understand and rebuild it as yours — the data model, the pages, the automation, and the angle that makes your version better rather than a weaker copy.
No. A template is a structured artifact with a version number, an author, and a payload describing modules, pages, bindings, and behavior. Installing one produces working functionality, not a restyled screen.
Yes. Any of the four families can be published as a marketplace product with versions, offers, and pricing, and the platform handles checkout, entitlements, and payouts.
You are not force-upgraded. The newer version is available, the differences are visible, and you choose when to move — the same adopt-or-stay model used for page forks.
Create an account, explore the full builder console, and launch your first application on a custom domain. Nothing is charged while your application is still in development.
No credit card required. The console preview, the documentation, and the architecture reference are all readable before you sign up.
Get started free Read the docs