A reusable composition of Nodes, saved as one unit.
A Stack groups Nodes that work together — a campaign's ad account, tracker and landing page, say — into one named, reusable unit you can reference as a whole instead of hunting down each piece every time. Stacks are private to your account in this build, not a public sharing surface.
Compose a Stack
Compose a Stack — illustrative example
Click a Node to include or exclude it from the Stack below.
One named, reusable unit — reference it as a whole in a Workflow instead of hunting down each Node every time.
A composition, not a bundle
A Smart Bundle is a Marketplace concept — a seller's curated group of Nodes sold together, before you own any of it. A Stack is the opposite: something YOU build, after acquisition, from Nodes already in your Network. The two share a shape (Nodes grouped together) but sit on opposite sides of a transaction.
Private in this build, by design
A Stack is scoped to your own account — there's no public Stack directory or sharing surface yet. That's a deliberate V1 boundary, not a bug: a Stack can hold real operational detail about how your Nodes work together, and until there's a real sharing model with its own permissions, keeping it private is the honest default.
What a Stack is for
Once Nodes are grouped, you can attach a Workflow to operate the Stack as one unit instead of touching each Node individually, and a Stack's shape can become the starting point for a new Template. Templates and Blueprints (see that page) is where a Stack's composition becomes reusable beyond the one instance you built.
Capabilities
What this is backed by: /stacks (shell-gated, requireActiveAccount()) — see docs/product for the current V1 scope.
Related Platform features