Documentation

What stacks are

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

Try StackShiftRead the overview

Stacks

What stacks are

Live

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

Goal

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

Current status

Live

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

Workflow

  1. 1Choose stacks when the workload is multi-container or service-like.
  2. 2Expect stack deployment to preserve service topology, volume configuration, and template provenance when relevant.
  3. 3Use templates when you want the stack shape pre-curated for you.

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

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