Templates

How templates accelerate setup: marketplace, library, and relationship to Applications and Services.

Written By Zoro

Last updated 26 days ago

Templates are reusable blueprints that help you stand up Applications and Services faster than configuring every resource from a blank canvas.

A template encodes opinionated defaults: service types, wiring, and often environment variable placeholders; you can adjust after instantiation.

Where templates show up

  • Marketplace and library surfaces in the product (names may vary by release) list templates you can browse and apply.

  • Applying a template still creates normal Applications, Environments, and Services; templates are a starting point, not a separate runtime layer.

When to use templates

  • New products or demos where you want a known-good stack quickly.

  • Standard stacks your team repeats (for example app + database + cache) with shared conventions.

After deploy, you manage the result like any other application: deployments, logs, domains, and backups follow the same model as hand-built services.

See also