vertracloud.template.yaml, plus the sources it points to. Vertra Cloud reads the manifest and creates the apps and databases it describes, asks the person who uses it only the questions you declared, and undoes everything if any step fails. You write the template once; everyone who uses it gets the same result in one click.
What a template contains
A template with one app and no database creates just the app. A template with two or more services (apps, databases, Blob folders) creates a stack: one resource that groups them and keeps them connected.
Code or image
Every app service picks one source type. The choice decides the plan the user needs and whether they spend an image slot.
Three apps created from the same image template use one slot, and a newer version of the same template reuses it. A template of code never uses a slot. Limits per plan are in Plans and limits.
In both cases,
/app is the only persistent disk and the rest of the file system is read-only. Read Best practices before you write the first manifest.
Public, private or shared
You cannot publish to the public catalog from the dashboard. A community template goes through a pull request, a review and a test run; see Contribute to the public catalog.
Pick your path
Write the manifest
Every field, with an example of each.
Questions and placeholders
Ask the user for values and wire services together.
Private templates
Save an app as a template, link a GitHub repository, or use the editor.
Validate and test
Check the manifest from the CLI and try it as a private template.