Templates
Templates are ready-made projects: an app together with its database, volumes and generated passwords. Open Templates in the sidebar, pick one, fill in what it asks for, choose a server and click Deploy. Zenavo creates the project and starts deploying it.
| Template | What you get |
|---|---|
| Ghost | Blog and newsletters, with MySQL. Asks for the site's URL. |
| Gitea | Self-hosted Git with SQLite. Clone over HTTPS. |
| Memos | Lightweight notes. |
| Metabase | Dashboards and business intelligence. Needs about 2 GB of memory. |
| n8n | Workflow automation. |
| NocoDB | A spreadsheet interface for databases. |
| Umami | Privacy-friendly analytics, with PostgreSQL. |
| Uptime Kuma | Uptime monitoring. |
| Vaultwarden | A Bitwarden-compatible password manager. Needs HTTPS: add a domain before signing up. |
| WordPress | Websites and blogs, with MySQL. |
After deploying, give the app a domain under its service's Networking tab (Domains & HTTPS). Each password is generated once, when the project is created, and stays in the services' variables.
For anything else, import a Zeabur template or add services one by one.
Deploy button
Let others deploy a template, or your repository, on Zenavo from a README:
[](https://zenavo.app/deploy?template=umami)
| Link | Opens |
|---|---|
https://zenavo.app/deploy?template=<code> | The template's page, ready to deploy. Each template page shows its Markdown. |
https://zenavo.app/deploy?repo=<https Git URL> | A new project with the repository as its first service. |
https://zenavo.app/deploy?image=<image> | A new project with the image as its first service. |
People who aren't signed in are asked to sign in or create an account first, and then continue where the button led. On a self-hosted control plane, use its address instead of zenavo.app.