Skip to content
Helicarrier Cloud

Templates & blueprints

Templates let you stand up a whole stack in one step instead of creating each service by hand, and let you capture a project’s shape to reuse or share.

First-party templates

Section titled “First-party templates”

The + New menu includes a catalog of ready-made stacks. Picking one stages the services as a changeset you review before applying.

  • Databases — PostgreSQL, MySQL, Redis, MongoDB, plus combos like Postgres + Redis.
  • Apps — one-click n8n (workflow automation, backed by a managed Postgres) and Evolution API (WhatsApp gateway, backed by Postgres + Redis). These come fully wired: the app connects to its managed database(s) automatically, a strong encryption key / API key is generated for you on each install, and the app’s own public URL is set so webhooks work out of the box. Review the stack (rename services, resize plans) and apply.

Export your project as a template

Section titled “Export your project as a template”

You can export any project to a *.heli-template.json file. The export captures the project’s structure — its services, their settings, and the references between them — but redacts secrets (env values aren’t included), so it’s safe to share or check in.

Import a template

Section titled “Import a template”

Import a template two ways:

  • By file — upload a *.heli-template.json.
  • By URL — point at a hosted template (fetches are SSRF-guarded).

Either way it’s staged as a changeset: you review the services (and can rename them) and see a monthly cost estimate before applying.

Deploy from docker-compose

Section titled “Deploy from docker-compose”

Already have a docker-compose.yml? Paste it or fetch it by URL and Helicarrier turns it into a blueprint: database images map to managed engines (e.g. postgres → a managed PostgreSQL), connection URLs are rewired to service references, and services with a build: become git-sourced. You review the result in two steps before it’s created.

Next

Section titled “Next”