Skip to main content
To use a template, open it in the gallery, click Use template, answer the wizard and click Create. Vertra Cloud creates every service as one operation, waits until the app is healthy and shows the outputs (address, generated passwords, next steps). If any step fails, everything the template created is removed and you see which step failed. Only the owner of a workspace can use a template inside it. A workspace member sees the templates but cannot deploy them: ask the owner. A template that belongs to a workspace deploys only inside that workspace, never into a personal account or another workspace. The gallery lists the templates available to you. In the dashboard, open Templates in the sidebar, which has three tabs: Catalog, My templates (your private ones) and In use (the apps and stacks you created from templates, with a New version available badge when there is an update).
  • Search and categories: automation, AI agents, bots, APIs, CMS, monitoring, starter projects, databases and other.
  • Fits my plan: shows only what your account can use right now, with your free memory and free image slots on each card. A template that does not fit says why.
  • Sort: recommended, most used, new, or A to Z.
  • Badges: Vertra, Community, Private and From the workspace. See the three origins.
Each template page shows what will be created (services and total memory), the requirements, the documentation, the version with its changelog, the license of the packaged software and the Use template button. You can also start from New in the dashboard, on the Templates tab.

​
Step by step in the wizard

1

Name and destination

Name the app (or the stack, when the template has several services) and choose the workspace and folder.
2

The template's questions

Answers appear in order, and some questions only appear depending on earlier answers. A question can be a text, a number, a yes or no, a choice or a secret. Questions the platform generates (such as an encryption key) are filled for you.
3

Memory of each service

Pick the memory of each service within what the template allows. The wizard shows “needs X, you have Y free”.
4

Subdomain

If a service has web, choose a subdomain or leave it random.
5

Summary

Review what will be created, the required plan and the image slots.
6

Create

Follow the progress by step: validation, databases, images, apps, variables, certificates, start and health check.
Only one template deploy per account runs at a time. A second one returns TEMPLATE_DEPLOY_IN_PROGRESS.

​
What is created

The databases are ordinary managed databases, each with its own memory taken from your plan. The connection variables and certificates are injected for you: see Connect apps to databases in a stack. Everything created from a template is linked to the version it came from, so you can update it later.

​
Outputs and one-time secrets

When the job finishes, the wizard shows the template’s outputs: the address of the app, the next steps and any generated credentials. An output marked as a secret that is shown once appears on the first read of the finished job and is gone afterwards. Copy it before leaving the page. The same applies to the CLI, the MCP server and the API.
A secret shown once cannot be read again. If you lose it, change it in the app (for example, reset the admin password inside the software) rather than looking for it on the platform.

​
If the deploy fails

The job undoes everything it created, in reverse order. Before it deletes an app or a database it takes a safety snapshot, because the database may already have accepted connections and the app’s /app may have changed. The error carries a stable code and the step that failed, for example TEMPLATE_RAM_INSUFFICIENT in the validate step. See the error reference for causes and fixes.

​
Use a template from the CLI, MCP or API

deploy asks the template’s questions in the terminal (secrets are typed without echo), follows the steps and prints the outputs at the end. Answer ahead with --set <question>=<value>; --yes, --json or a non-terminal session ask nothing and fail listing every missing answer. --service <service>.ram=2048 sets memory per service, and --share <link> deploys from a share link. See the CLI reference.
The public catalog can be read without authentication; with a key, each template also carries whether it fits your plan and free memory.

Stacks

What a multi-service template creates.

Update and roll back

New versions of a template.
Last modified on October 30, 2026