Skip to main content

What Is a Stack

A Stack is a deployed instance of a catalog template inside a tenant workspace. When a tenant deploys an application — Superset, Trino, Airflow — a Stack is created that represents that running deployment. The Stack tracks which template version it was deployed from, the inputs provided, and the current state of everything inside it.

Atomic and Composite Stacks​

Atomic stacks define their own resources directly. Each atomic stack is a self-contained deployment unit — one application, one set of inputs, one lifecycle. Destroying a JupyterHub stack does not affect the Airflow stack next to it.

Composite stacks reference other atomic stacks and compose them into a bundle. Deploying a composite stack creates one independent child stack per included atomic template. Each child has its own lifecycle.

The Bundle​

The source of truth for a stack is its bundle.yaml file — a declarative spec that defines inputs, resources, and how they relate. Bundle files live in the Platform Stacks repository and are registered into the Control Plane catalog.

Go Deeper​