What Is Stacker?

Stacker is the stack engine behind a lot of the more technical TryDirect workflows.

At a simple level, it helps teams turn a project into a deployable stack using one readable configuration file, then deploy, inspect, and evolve that stack more intentionally.

If you only know the product-facing side, the easiest way to think about Stacker is this: Stack Builder helps shape the stack in the UI, and Stacker is the engine and CLI that make the stack explicit, reusable, and operable.

Before you run the commands

If you do not have Stacker installed yet, the quickest path is the install script.

curl -fsSL https://raw.githubusercontent.com/trydirect/stacker/main/install.sh | bash

GitHub repository and installation steps

If you prefer to explore Stacker with Docker first, you can also pull the image:

docker pull trydirect/stacker:latest

If your workflow also uses Status Panel locally or on a target server, start here too.

curl -sSfL https://raw.githubusercontent.com/trydirect/status/master/install.sh | sh

GitHub repository and installation steps for Status Panel

docker pull trydirect/status:latest

What Stacker does

• generates a stack definition from a local project
• creates Docker and Compose artifacts from that definition
• deploys locally, to existing servers, or to cloud targets
• helps teams inspect health, logs, and runtime state
• supports a marketplace workflow for reusable stack templates

Why teams use it

Stacker is useful when a project has grown beyond “just run this Compose file once” and the team needs a more durable workflow.

• developers who want repeatable local-to-remote deployment
• agencies packaging reusable stack patterns for clients
• teams experimenting with AI products such as OpenClaw, n8n, and vector databases
• operators who want the stack definition and the runtime workflow to stay connected

Common commands

stacker initstacker init --with-aistacker deploystacker statusstacker agent statusstacker marketplace status

How it relates to TryDirect

TryDirect uses a product-facing web experience, while Stacker gives more technical users a CLI and stack-native workflow that supports the same broader goal: build, deploy, operate, and reuse multi-service systems more cleanly.

Good next reads

If you want a practical example, start with the OpenClaw guide in explains.