Zero Stack

Zero Stacks

What is Zero Stacks?

Explore what a stack contains, how installation creates a separate set of resources for each team, and how connections turn a packaged process into working software.

  • Supplier risk stack
    • Flow Supplier review
    • Dataset Supplier master
    • Agent Risk summary
    • Approval High-risk exception
    • Schedule Daily at 08:00

  1. 01

    Package

    Choose the capabilities and flows that make up the solution.

  2. 02

    Install

    A team or client gets their own copy of each one.

  3. 03

    Connect

    The copies are pointed at that team's own systems.

  4. 04

    Start

    The work begins when they are ready.

Installing puts everything in place. The first run starts when the team chooses, or when the stack's schedule first comes due.

More stacks

  • Document check

    A flow, a dataset of incoming files, and an approval for the documents that need a second look.

  • Morning digest

    A schedule, a Research agent, and a dataset the digest is written to.

  • Client onboarding

    The same set of capabilities, installed for each new client and connected to that client's systems.

Acme: their own copy

Connected to Acme's purchasing system. Runs for Acme alone.

Birchfield: their own copy

Connected to Birchfield's purchasing system. Runs for Birchfield alone.

Each installation has its own resources and connections.

What is a stack?

A stack is a packaged solution: any mix of capabilities and flows, installed as one unit for a team or client.

What can a stack contain?

Flows, agents, datasets, approvals, and schedules, in any combination. A stack can hold a full process, or a set of capabilities with no flow.

What happens when a stack is installed?

The team or client gets their own copy of everything in it, connected to their own systems. Installing puts the solution in place, and the work starts when they are ready.

How does a stack differ from a flow version?

A flow version defines one released process. A stack packages the capabilities and flows needed for a broader solution.

How does a stack work for different teams?

Each team installs its own copy and connects it to its own systems. Their resources and work remain separate.

Stack

A packaged set of capabilities and flows, installed as one unit for a team or client.

Install

Creating your own copy of everything in a stack, connected to your own systems and ready to start.

Capability

One focused building block, such as an agent, a dataset, an approval, or a schedule, that is useful on its own and as a step in a flow.

Flow

The definition of a business process: its steps, data, decisions, and order.

Connection

Zero's link to an external system you already run. It holds the credentials and settings that other capabilities use.

Zero Stacks is part of Zero, the agentic orchestration platform.