Templates
A template is a reusable application stack configuration with setup questions and operating instructions. It can contain one service or several connected services, such as an application and its private database. Deploying it creates a stack on an existing resource pool.
The public registry adds publisher identity, immutable releases, reviewed image digests, supported architectures, resource requirements, uploaded assets, and release documentation. Browse the public Templates catalog or Templates in the dashboard to see currently published inventory.
Choose a starting point
| Path | Choose it when |
|---|---|
| Published registry template | You want an available reviewed release with setup inputs and maintenance guidance |
| Starting configuration in the stack editor | You want to build from a configuration currently offered there |
| Custom stack | You need your own source builds, private images, or service layout |
The stack editor includes built-in starting definitions for WordPress, PostgreSQL, MySQL, MariaDB, and Redis. Available starting entries can also come from the registry. These definitions and private publisher drafts are not a promise that every application is published in the public catalog. Use the catalog’s actual release availability when selecting a registry installation.
What a registry release contains
- Application name, summary, category, tags, and icon.
- Publisher handle, public profile, and verification indicator when applicable.
- Template version, upstream software version and edition, and license links.
- Supported Compose services with public images pinned to immutable digests.
- Private input definitions, optional defaults, generated secrets, and supported derived database URLs.
- Minimum CPU, memory, storage, and declared tested Linux architectures.
- Required external services and resource assumptions.
- Description, getting-started instructions, operations and backup guidance, and release notes.
- Optional uploaded screenshots with alternative text.
A template version identifies a configuration release such as 1.1.0. An upstream version identifies the packaged software. An installed stack revision records your deployment configuration. These identities are related but not interchangeable.
Release and publisher identity
Templates live under a publisher namespace, such as /templates/publisher-handle/template-slug. Release pages identify an exact version, and published release content is immutable. An installation retains the originating release identity and content hash even if its service configuration is later customized.
A verified publisher checkmark indicates reviewed identity and maintenance evidence. It is not an upstream partnership, a security certification, or a guarantee that an application is free of vulnerabilities. Each release still goes through review.
Review and operating responsibility
Registry publication requires static configuration validation and current rights, image-scan, installation, and persistence evidence for the declared architectures. Staff record and review evidence from real external checks and disposable test infrastructure; submitting a draft does not run the application in the review portal.
Review does not replace your own configuration, security, backup, and upgrade decisions. Public templates use public prebuilt images; source builds and private registry references are not supported in public releases. Use a custom stack for those requirements.
Installation and updates
Choose a release, read its setup and operations instructions, select an eligible pool, answer the inputs, and review the services before deploying. Generated secrets are created privately for the new installation. See Deploy a template.
Installed stacks keep their configuration. Publishing a new template version never automatically upgrades an installed stack. Advanced configuration changes can mark an installation Customized configuration while retaining its original release identity. See Releases and maintenance.
Deploying a template does not buy or resize infrastructure. Applications share the selected resource pool’s capacity; software licenses and external services may have separate charges. Read the release’s requirements and billing guide.
Publish your own
A workspace owner can create a publisher and delegate editing or administration to accepted workspace members. Authors prepare metadata, permitted assets, Compose configuration, input definitions, and operating documentation, then submit an immutable candidate for staff review.
Start with Create and publish templates, then use the input reference and Compose reference while authoring.