Skip to content

Quickstart: Deploy a Template

Clank includes 27+ one-click templates for popular open-source applications. Templates come pre-configured with companion databases, persistent volumes, environment variables, and resource limits — deploy a production-ready stack without writing any configuration.

From anywhere in the dashboard, press Cmd+K (Ctrl+K on Windows/Linux) or click the + button in the sidebar. Select New from Template.

Templates are organized by category:

  • AI & Agents — Open WebUI, Flowise, LiteLLM
  • Websites & Publishing — WordPress, Ghost
  • Backend & CMS — Supabase Studio, Directus, NocoDB
  • Automation & Internal Tools — n8n, Appsmith
  • Analytics & Monitoring — Umami, PostHog, Metabase, Uptime Kuma
  • Business & Ops — Cal.com, Chatwoot, Listmonk
  • Developer Tools — Gitea, Paperless-ngx
  • Databases — PostgreSQL, MySQL, MongoDB, Redis

Use the search bar to filter by name, or browse by category.

Click the template you want. The detail panel shows what will be deployed: the main application image, any companion services (like a database), resource limits, and the volumes that will be created.

For example, selecting WordPress deploys:

  • WordPress container with a persistent volume for /var/www/html
  • MySQL companion database with a persistent volume for /var/lib/mysql
  • Pre-configured environment variables connecting WordPress to MySQL
  • Resource limits based on the application’s recommended specs

Select an existing project or create a new one. Choose which server the template deploys to.

Click Deploy. Clank pulls the images, creates named volumes, sets environment variables, starts the containers, and waits for the health check to pass. The deployment log streams each step.

Once all services show Active status, click the URL in the service panel. Most templates include a setup wizard on first launch — for example, WordPress prompts you to create an admin account and choose a language.

Every template is configured with sensible defaults:

  • Companion databases — Applications that need a database (WordPress, Ghost, n8n, etc.) include one automatically. The database credentials are pre-generated and injected as environment variables.
  • Persistent volumes — Data directories are mounted to named Docker volumes so your data survives redeployments and container restarts.
  • Resource limits — CPU and memory limits are set based on each application’s official recommendations.
  • Health check paths — Web applications include a health check endpoint so Clank can verify the service is responding before routing traffic to it.