Templates and Managed Databases

One-click stacks from a maintained catalogue, and provisioned databases.

The template catalogue ships 160+ maintained open-source applications — analytics, CMS, automation, media, security and backend platforms. Each template documents its first-run setup and connection details, so a one-click deploy is still an informed one.

Creating a service from a template#

Open the Templates picker from the New Service flow, search or browse by category, and choose a stack. Templates declare their variables — some prompt for a required value on first deploy, others use a persisted default; values are encrypted at rest when marked secret. Template variables can reference the platform variables ${ZENSAILOR_DATA_PATH}, ${ZENSAILOR_SERVICE_ID} and ${ZENSAILOR_PROJECT_NAME}.

Databases#

The Databases view provisions 20 database and data-store engines. Managed engines — PostgreSQL, MariaDB, MongoDB, Redis and TimescaleDB — receive:

  • durable storage through the platform's persistence rules,
  • generated credentials, and
  • a collision-safe private-network alias plus a connection variable such as DATABASE_URL wired into the environment of a service you choose.

Each connection key is owned by one service per environment, so two services never fight over the same injected credential.

Add-ons from the CLI#

BASH
# List available addon templates
zensailor addon list

# Provision a managed database for the current service context
zensailor addon provision postgres
zensailor addon provision redis
zensailor addon provision mongodb
zensailor addon provision mariadb

One owner per connection key: if you need two apps to share a database, connect them to the same provisioned engine rather than provisioning twice — each environment keeps a single canonical connection for a key.