Documentation

What templates are

Templates are versioned service blueprints that render into stacks with saved inputs and provenance.

Try StackShiftRead the overview

Templates

What templates are

Live

Templates are versioned service blueprints that render into stacks with saved inputs and provenance.

Goal

Understand templates as a managed service-deployment layer on top of stacks.

Current status

Live

This area is documented as current, user-reliable behavior.

Workflow

  1. 1Treat templates as a deployment product, not a separate runtime.
  2. 2Expect template-backed stacks to preserve version and input history.
  3. 3Use template lifecycle tooling to preview and apply updates safely.

Why templates exist

Templates make common services easier to deploy and maintain by pairing a stack blueprint with defaults, service notes, lifecycle metadata, and safer update behavior.

What templates add on top of stacks

  • Saved deployment inputs and secret handling
  • Version tracking and upgrade previews
  • Readiness notes, operator guidance, and safer update paths

Expected result

You can explain why templates are different from pasting raw Compose into a stack.