QuickStackQuickStack
How To

App & Database Templates

Deploy one-click apps and databases from QuickStack templates: WordPress, Nextcloud, n8n, Gitea, LiteLLM, PostgreSQL, and more.

Templates are predefined applications and databases you can deploy in a few clicks. A template ships with a container image, environment variables, persistent storage, and the internal networking rules it needs, so you do not have to assemble a Docker Compose file yourself.

For apps where you control the source code, image, or Dockerfile, use a regular application instead.

Create an app from a template

You can start from the toolbar or from the network graph:

  • Toolbar: click Create App → Template.
  • Network graph: right-click an empty spot on the canvas and choose Create App from Template.

Databases have their own entry: Create App → Database, or right-click → Create Database. See Deploy Databases for the database workflow.

The Create App from Template dialog lists the available templates with their icon, name, description, and an App or Database badge. Use Search templates... to filter the list.

Review and create

Selecting a template opens a setup dialog titled Create App "<template>":

  1. Rename the app if needed in App Name.
  2. Fill in the template's input fields. Common examples are Container Image, database credentials, admin username/password, and timezone. Fields marked If left empty, a random value will be generated. are filled with a secure random value when left blank.
  3. Review the Selected template panel, then click Create app.

Ports, volumes, file mounts, and static environment variables are prefilled by the template and are not shown in the create dialog. You can change them afterward through the app's normal settings.

Deploy after creating Creating the app does not start it. Open the app and click Deploy to build or pull the image and start the workload.

Application templates

TemplateDescriptionBundled services
WordPressPublishing platform and CMSMariaDB
n8nWorkflow automation—
NextcloudFile sync, share, and collaboration—
MinIOS3-compatible object storage—
Uptime KumaUptime and service monitoring—
GiteaLightweight self-hosted Git service—
DocmostCollaborative documentation and wikiPostgreSQL, Redis
NGINXWeb server and reverse proxy—
AdminerDatabase administration UI—
draw.ioDiagram editor—
DuplicatiBackup client—
Open WebUIWeb UI for local LLMsOllama
Apache TikaContent extraction toolkit—
LibredeskCustomer support deskPostgreSQL, Redis
Chisel TunnelTCP/UDP tunneling over HTTP—
LiteLLMLLM gateway / proxyPostgreSQL, Redis

Templates that bundle several services create all of them as separate apps in the same project and wire up the internal network rules and connection environment variables automatically.

Database templates

TemplateDefault imageDefault portDefault volume
PostgreSQLpostgres:18-alpine5432300 MB
MySQLmysql:93306500 MB
MariaDBmariadb:113306400 MB
MongoDBmongo:727017500 MB
Redisredis:8-alpine6379200 MB

Database templates deny internet access by default and store credentials as environment variables. See Deploy Databases for connecting apps and accessing credentials.

Editing a deployed template

A template is only a starting point. After creation, every app is a normal QuickStack app: change the image or source, environment variables, domains, storage, replicas, and resource limits, then redeploy.

Do not change generated database environment variables For database apps created from templates, leave the automatically generated credentials (POSTGRES_PASSWORD, MYSQL_ROOT_PASSWORD, and similar) untouched unless you also update every app that connects to it.

On this page