Which applications can I find in Templates?
The catalog can include common applications such as n8n, Metabase, and WordPress. Choose a Template, confirm deployment, and receive a ready project.
Templates
One-click deployment with Templates
Choose apps such as n8n, Metabase, and WordPress and publish a ready-to-run project in a few steps, with settings you can review before deployment.
A starting point ready to publish
Templates combine an application, suggested settings, and expected variables to turn a technical process into a simple guided flow.
Choose a Template
Find ready-to-run n8n, Metabase, WordPress, and other common application Templates, as well as your organization’s private Templates.
Review the essentials
Name, plan, capacity, and other options arrive filled in, with freedom to adjust them before publishing.
Deploy in one click
Confirm the information, fill only what is necessary, and let Zenifra prepare the new project.
When to use Templates
A practical path for teams that want to share standards without turning every deployment into configuration from scratch.
People who have never deployed
Choose n8n, Metabase, WordPress, or another ready application and get it running in one click.
Organizations that share good practices
Publish public templates to help other organizations start with fewer repeated decisions.
MVPs and internal tools
Use a ready Template, review capacity and variables, and publish the first project in a few steps.
How the flow works
From private creation to the public catalog, each step keeps authorship, permissions, and new-project choices clear.
01
Create a starting point
Set the application, port, persistence, capacity defaults, and variables the project expects.
02
Publish when ready
The template starts private and can be published after validation to appear in the public catalog.
03
Confirm and publish in one click
Review suggestions, fill only the necessary values, and create an independent project.
What the author defines
The template guides deployment without hiding important decisions from the person who will own the project.
Application
Use a public application reference compatible with Docker Hub, GHCR, Quay, or GitLab Registry.
Editable defaults
Plan, billing, exposure, instances, persistence, capacity, and auto-scaling arrive prefilled.
Variables
Declare names and descriptions to guide deployers. Secret variables never receive a default value.
Version
Each revision is preserved in the created project so a future change does not alter what was already deployed.
Before publishing
Validate the application and review standards before making the template public. The catalog should explain the starting point, not replace each organization’s decision.
- HTTP application ready to share
- Port and persistent folder confirmed when applicable
- Plan, billing, and initial capacity reviewed
- Secret variables separated for deployment
- Organization permissions reviewed before publishing
Template catalog
The screen combines the active organization’s templates and the public catalog, ordered by recency or usage.
Choose a common everyday application, click to deploy it, and let Zenifra deliver a project ready to use.
Frequently asked questions
Short answers to understand what a template does before opening the catalog.
Do I need cloud knowledge to use a Template?
No. The Template includes the main settings for you to review before confirming deployment.
Do Templates replace the original project?
No. A template is a starting point; each deployment creates its own project.
Who can see a private template?
Only people in the same organization who have access to the template.
Can I publish any application?
The flow supports HTTP applications with public references in supported registries.
Does using a template generate charges?
Billing follows the plan and mode selected at deployment; the template only suggests those values.