Templates
Deploy popular open source apps by filling in a short form.
A template deploys a whole app in one go: the app itself, the databases it needs, generated passwords, and the wiring between them.
Deploy a template
Pick one
Open the command panel in a project, choose Template and pick an app.
Fill in the form
Most templates ask for a domain and a storage size. A generated domain is suggested, or type your own. Less common inputs sit behind more inputs.
Deploy
Press Deploy. Unbind creates a service group with everything inside and starts the services in the right order. Databases come up first, and the app waits for them.
Each template's page says how to sign in afterwards. Generated passwords and keys are always in the variables of the service named there.
Available templates
Appsmith
Admin panels and internal tools
Convex
Reactive backend with realtime sync
Flowise
Visual builder for LLM apps
Formbricks
Surveys and feedback
Ghost
Blog and newsletter platform
Gluetun
VPN client with an HTTP proxy
Listmonk
Newsletters and mailing lists
Meilisearch
Fast search engine
MinIO
S3 compatible object storage
n8n
Workflow automation
NocoDB
Databases as spreadsheets
Plausible
Privacy friendly analytics
PocketBase
Backend in a single service
Supabase
Open-source Firebase alternative
Teable
Airtable alternative on Postgres
Umami
Simple web analytics
WireGuard
Your own VPN
WordPress
The most used CMS
After deploying
A deployed template is a set of normal services. You can change variables, add domains, resize volumes and read logs like anywhere else.
- Updates: templates pin a version of the app. To move to a newer one, change the image tag on the service. Read the app's release notes first, because some upgrades need manual steps.
- Existing deployments stay as they are. When a template changes in a new Unbind release, only new deployments use the new version.
- Storage only grows. Pick sizes that fit now and expand later.