Skip to main content
A template is a ready-made recipe that creates an app, or a group of connected apps and databases, in one step. You pick it, answer a few questions and Vertra Cloud builds everything, wires the connections and hands you the address and the credentials. If any step fails, everything the template created is removed. Any plan can use code templates, such as the Discord bots, as long as the account meets the template’s requirements: free memory and web publishing. Image templates (n8n, OpenClaw, Hermes Agent, Evolution API, Open WebUI and Uptime Kuma) need a plan with custom Docker images, which today means Enterprise 28, 30 or 32, and a free image slot. See Plans and limits for what each plan includes.

​
What a template creates

Everything a template creates is an ordinary resource of your account. The app’s /app folder is its persistent disk, and the rest of the file system is read-only, the same as any other app on the platform.

​
Code templates and image templates

Each app in a template comes from one of two sources, and the source decides what the template costs your plan. The Discord bot templates are code templates. n8n, OpenClaw, Hermes Agent, Evolution API, Open WebUI and Uptime Kuma run an image. See the catalog.

​
The three origins

Every template carries a badge that says where it comes from. Public templates (Vertra and Community) never contain secrets: anything sensitive is asked of you or generated for you when you use the template. To publish your own, see Create templates.

​
How the required plan is computed

The platform works out the plan a template needs from what it will create, with your answers to the wizard included, and compares it with your account. The required plan is the higher of two things:
  • Computed requirements: the sum of the minimum memory of every service must fit in your free memory; a service with web needs web publishing; an image service needs a plan with images and a free image slot; a Blob folder needs a plan with Blob Storage; the plan’s limits of apps and databases and its hourly limit of deploys must leave room.
  • Declared minimum plan: an author may also require a minimum plan for commercial reasons.
A template can restrict what your plan allows (for example, turning off deploys without downtime), but it never unlocks anything your plan does not include. When the account does not fit, the gallery card and the template page say why (“needs 2 GB of free memory”, “needs a plan with images”) and the button leads to the upgrade. The wizard shows “needs X, you have Y free” for memory. Plan numbers are on Plans and limits.

​
Image slots

A template that runs an image uses one image slot per distinct image, never one per app. Three apps created from the same template use one slot, and a new version of that template uses the same slot. The slot is released when the last app that uses the image is gone (if a template deploy is running in the account at that moment, the slot is released when it ends). In your images list, the slot appears as “n8n (template)” with no rebuild or edit actions. Slots count toward the same limit as custom Docker images.

​
Where to go next

Use a template

The gallery, the wizard, what is created and the outputs.

Stacks

How apps, databases and Blob folders live together.

Update and roll back

New versions, the safety snapshot and rollback with data.

Catalog

The official templates.
Last modified on October 30, 2026