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

> Stacks are the service-oriented workload model in StackShift, built around Compose, named volumes, and node-aware placement.

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

## Goal

Know when to use a stack instead of a project or template.

## Prerequisites

* Familiarity with Docker Compose

## Workflow

<Steps>
  <Step>
    Choose stacks when the workload is multi-container or service-like.
  </Step>

  <Step>
    Expect stack deployment to preserve service topology, volume configuration, and template provenance when relevant.
  </Step>

  <Step>
    Use templates when you want the stack shape pre-curated for you.
  </Step>
</Steps>

## Good fits for stacks

* Service bundles like MinIO, Grafana, and internal tooling
* Multi-container applications with support services
* Stateful workloads that rely on named volumes

## How stacks differ from projects

Projects are the app-deployment surface. Stacks are the service-system surface. That difference matters because stacks carry Compose topology, named volumes, node placement decisions, and template provenance in ways projects do not.

## Expected result

<Check>
  You can pick stacks intentionally instead of treating them as “projects but bigger”.
</Check>

## Related guides

<CardGroup cols={2}>
  <Card title="Deploy a Compose stack" href="/stacks/deploy-a-compose-stack">
    Bring a Compose-defined workload to StackShift with domains, placement, and persistent volumes.
  </Card>

  <Card title="What templates are" href="/templates/what-templates-are">
    Templates are versioned service blueprints that render into stacks with saved inputs and provenance.
  </Card>
</CardGroup>