Circuit coordinates available compute across multiple Garages while applications continue addressing services by logical identity.
Circuit turns heterogeneous machines across data centers and edge nodes into a unified execution pool.
Use available lanes, queue pressure and artifact locality to choose execution capacity in real-time.
Prefer already prepared or locally cached Components when useful to minimize cross-network transfers.
Applications keep using pit://service regardless of which Garage executes the work. Machine boundaries stay hidden.
Coordinate compute hosts with simple, declarative CLI commands.
# 1. Join a local or edge Garage into an active Circuit
pit circuit join --garage edge-a --token $CIRCUIT_TOKEN
# 2. Inspect active Garages, total lanes, and lane availability
pit circuit status
# 3. Route workload explicitly to optimal Garage
pit call pit://service-a/eval --placement autoEvery subsystem handles one distinct responsibility in the demand-driven execution chain.
Scale compute capacity across machines without managing Kubernetes nodes or complex networking meshes.