Create a template

Create template is the designer where you build Personal templates for your Organisation. Saved work appears under Templates → Personal. You can Deploy from Deploy from template (Personal tab) or Publish to Community when you are ready.

PrerequisitesCopy Anchor Link

• Access to create and update templates (see Roles and permissions if buttons are missing).
• Integrations for Git and container registries when you use organisation connections instead of pasting credentials.
• Each app must use GitHub, GitLab, Bitbucket, Azure DevOps, or Gitea, or that app will be skipped when others deploy the template.

Start from an empty templateCopy Anchor Link

1. Open Templates.
2. Click Create template.

You get a large canvas. Add App, Database, and Docker blocks from the toolbar, connect them if you want to show relationships, and open each block to fill in settings. A deployment order section lets you reorder services for clarity.

While you are not editing an existing template, your layout may be restored after a browser refresh (stored locally in your browser). Clearing site data clears that draft.

Convert an Application into a templateCopy Anchor Link

1. Open the Application you want to copy.
2. Choose Convert as Template (available when the application has Services).
3. Enter a template name and description, then Create.

That saves a new Personal template built from the application’s services (service names, variables, and volume paths are adjusted so they are not tied to the old application prefix). You are then sent to the designer (compose) to adjust the graph, variables, and order; use Save template whenever you want to persist further changes.

Configure each type of serviceCopy Anchor Link

App: Choose the Git host, then repository, branch, build path, port, and tokens or linked Git provider as needed. Azure DevOps expects a token.

Database: Pick the engine and optional exposed ports.

Docker: Set the image reference, optional registry, and port mappings.

Environment variablesCopy Anchor Link

Add variables per service. To reference another service, use {{ otherServiceName.KEY }}. Key rules are in Template configuration.

Deployment orderCopy Anchor Link

Drag to reorder in the UI so readers understand the stack. Deploy still brings databases up before apps and Docker pieces automatically.

SaveCopy Anchor Link

1. Click Save template (needs at least one service on the canvas; disabled when you are only viewing an Official or Community template).
2. Enter Name (at least 3 characters), Description, and optionally an image for the card.
3. Confirm Create or Update.

New saves are Personal to your organisation. Replacing the card image removes the previous image from storage when save succeeds.

View-only Official or CommunityCopy Anchor Link

Opening the designer from a catalogue template lets you explore the graph but not save over it. Recreate what you need under Personal to make changes.

Edit a Personal templateCopy Anchor Link

On Templates → Personal, use ⋯ → Edit, adjust the graph, then Save template again.

Expected outcomeCopy Anchor Link

The template is listed under Personal, ready to Deploy or Publish.

Next stepsCopy Anchor Link

• Publish a template
• Deploy a template
• Template best practices

RelatedCopy Anchor Link

• Template configuration
• Integrations overview