Every service is its own repository with its own releases, so nothing here has to be adopted whole. If you want all of it, one command brings it up on a box you own. If you want one piece, it installs and runs on its own. The exact commands, pinned to a version, live in each repository, because a second copy of an install procedure is a second thing to keep true.
A Debian or Ubuntu machine you own, one command, every service pulled as a published image and nothing compiled.
One command ↓The same services as plain manifests: one script for bare servers, or one apply on a cluster you already run.
The cluster ↓Built from source and run natively, with no Docker, bound to your own machine and gone when you press Ctrl-C.
The sandbox ↓Any single service from its own repository. Most run on their own; the list says which lean on another.
The list ↓You need a Debian or Ubuntu machine you control, root on it, and outbound internet. Everything else the installer brings: it adds Docker if the machine has none, pulls every service as a published image, and compiles nothing.
It brings up the core: the gateway and the ledger behind it, policy, identity, key custody and its witness, alerts by mail, a check on the record's chain, the console, and the tunnel an operator uses to reach it. It ends by checking itself, and the last line it prints says whether every check passed.
It comes up closed. The gateway listens on the machine's loopback, so nothing faces the internet until you open it, and opening it is one word:
Then point an agent at the gateway, wherever that agent runs. Every call carries a client key, and the installer mints one for your agents when you bring none, in /opt/agent-stack/agent-key.
To check an installed box again without changing anything on it:
WITH_DELEGATION=1 ./install.shWITH_TYPED=1 ./install.shdocker compose --profile egress up -d scopyxdocker compose --profile finops up -d costcrewEvery flag, and what a second run does and does not change, is in the stack-single repository.
The same services as plain YAML and a kustomization, with no Helm. On bare servers, one script builds the cluster and the stack together:
That script is written for Hetzner: it puts up the cloud firewall, a cluster with secrets encrypted at rest and network policy that is actually enforced, and storage, then applies the manifests and runs the stack's own checks and its containment tests. AWS and GCP have deploy scripts of their own, and on a cluster you already run the manifests apply with one command:
Some services are opt-in on a cluster too, each one more manifest to apply. The stack-k8s repository names them, along with every trap found while building it.
A sandbox, not a deployment. It builds each service from source and runs it natively, with no Docker, binds everything to 127.0.0.1, and stops cleanly when you press Ctrl-C. If a toolchain or a port is missing, it says which.
Delegation, the FinOps console and typed answers join with --with-delegation, --with-finops and --with-typed. The stack-up repository has the port map and the rest.
Nothing here has to be adopted whole. Each service is its own repository with its own releases, and most of them run alone. The list says how each one ships and what, if anything, it leans on; its repository has the command, pinned to a version.
| service | how it ships | on its own | install |
|---|---|---|---|
| the control room | |||
| Genaryx | The console of the one-box and cluster installs; built from source on its own. | Reads the stack it sits on. | genaryx ↗ |
| money | |||
| TokenFuse | A container image: a proxy you start and point your agent at. | Yes, with a model provider behind it, or its stub for a dry run. | tokenfuse ↗ |
| CostCrew | A Go binary, or the finops profile of the one-box install. | Yes. It listens on loopback and reads your bills. | costcrew ↗ |
| TokenFuse Pocket | An iPhone app, not wired in yet, so there is nothing to install. | Not yet. | not yet |
| guardrails | |||
| Wardryx | A signed container image, or built from source with Go. | Yes. It answers policy questions over HTTP. | wardryx ↗ |
| Idryx | A prebuilt binary for your platform. | Yes. It reads an event log. | idryx ↗ |
| Scopyx | A container image. | Asks Wardryx for every decision. | scopyx ↗ |
| Vouchryx | A container image. | Needs an issuer, a signing key and the issuers it trusts. | vouchryx ↗ |
| proof | |||
| Qryx | A prebuilt binary, with checksums. | Yes. Point it at a path. | qryx ↗ |
| Keyryx | A container image whose build you can verify. | Holds the signing keys the others use; the one-box install includes it. | keyryx ↗ |
| Verdryx | A Python package, installed from its repository. | Yes. A dry run uses a stub model, with no network and no key. | verdryx ↗ |
| Typryx | A Go binary or a container image. An optional add-on. | Yes, on its stub backend until you choose a model. | typryx ↗ |
| Mockryx | A prebuilt binary. | Needs a pre-production gateway to fire its drills at. | mockryx ↗ |
| Trailryx | Container images: a receiver and a store. No Rust toolchain needed. | Takes events from the stack and keeps the record. | trailryx ↗ |
| ground | |||
| Heraldyx | A container image. | Reads an event file, and can write the mail to a file instead of sending it. | heraldyx ↗ |
| Engram | A Python package, pip install engdbram: a library in your own process. | Yes. | engram ↗ |
| Platform | Agent Passport is a specification; agent-stack-go is a Go module with the agent-conform binary; the Terraform provider is on the Terraform Registry as TAIPANBOX/taipan. | Yes, each of them. | agent-stack-go ↗ |
The guides index has the rest: how the stack is secured, the practice of running agents, and what changed in October.