> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# What templates are

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

<Tip>
  **Live.** This area is documented as current, user-reliable behavior.
</Tip>

## Goal

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

## Prerequisites

* Understand stacks

## Workflow

<Steps>
  <Step>
    Treat templates as a deployment product, not a separate runtime.
  </Step>

  <Step>
    Expect template-backed stacks to preserve version and input history.
  </Step>

  <Step>
    Use template lifecycle tooling to preview and apply updates safely.
  </Step>
</Steps>

## 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

<Check>
  You can explain why templates are different from pasting raw Compose into a stack.
</Check>