Why we stack

Vertical integration

Most business software is a federation of vendors held together by glue code. Every new client is a new integration. We collapsed it: one substrate, one engine fleet, one application layer, one client config. The vertical stack is the integration.

Ring 4

Client blueprints

Per-engagement config + brand pack.

SBR · New Era IT · per-future-client

Ring 3

System blueprints

Universal verticals. Re-usable across clients.

collections · field-services · trust-reconciliation · MSP · QMS · manufacturing · problem-solving

Ring 2

Shells

Operator-facing apps. The cockpit.

val-desk · val-forge (ADE) · val-up (Mission Control)

Ring 1

Engines

ValOS-owned services. The fleet.

val-grid · val-cargo · val-ontology · val-ledger · val-bay · val-agent · val-node · val-orchestrator · val-policy · val-up · val-forge

Ring 0

Substrate

Third-party dockers. The dial-tone.

postgres · openbao · nats · vllm · meilisearch · kamailio · freeswitch · meshcentral · hocuspocus

Why-1

Each ring only depends down.

Substitutions are bounded. Swap a Ring 0 docker, the engines keep running. Swap a Ring 3 blueprint, the client config moves with it. No circular dependencies.

Why-2

Vertical is the product.

Competitors sell horizontal SaaS (CRM, ticketing, ERP). They leave the integration as the customer's problem. We ship the full vertical — substrate to client config — as one install.

Why-3

30-day onboarding.

Ring 0–2 is the platform install (hours). Ring 3 is the vertical blueprint (days). Ring 4 is per-client config (a week). 30 days end to end. Slater Byrne is the validator.

The full layer-by-layer breakdown

16 numbered layers · status flags · per-layer ADR references

open checklist →