ComputeAPI
A commercial interface to capacity: GPU providers today; bare metal, common cloud adapters, and Bring Your Own Cloud management planned.
Explore capacity ↗The Service Automation Hub
Infrastructure,
with an
operating model.
Provision, configure, execute, and verify. SAH brings a family of infrastructure tools into a shared product direction—with clear boundaries for authority and execution.
Service Automation HubSystem map
01 / CAPACITYComputeAPI
02 / CONTROLSystemAPI
One lifecycle.Policy · evidence
Human intent
Human intent
03 / EXECUTIONadssh + vpscfgfarm
04 / VERIFICATIONbadfarm + goodfarm
Target architecture / joins in development↗
01 / The platform
Capacity meets control.
Use the APIs for infrastructure. Use the shell and fleet tools for the work that happens on it.
SystemAPI
Outbound Linux agents, live telemetry, Docker and Kubernetes operations, and entitled Starlark execution.
Explore fleet control ↗The SAH ecosystem
adssh, contracted fleet execution, independent discovery, repair coordination, and local tools for operators and agents.
Explore the tools ↗02 / The target workflow
From an allocation
to a verified outcome.
This is the lifecycle we are connecting. The pieces exist at different stages; the automatic handoffs are still in development.
Provision capacity.
Choose our infrastructure, a managed provider, or a customer-owned cloud account.
Enroll and authorize.
Bind host identity to the control plane. Scope the work through policy and a validated lease.
Execute and observe.
Use the agent or execution shell to perform the allowed operation and capture its result.
Verify and retain evidence.
Check the resulting state and preserve the evidence needed to explain the change.
03 / Availability
An honest map of the joins.
| Connection | Status | What it does |
|---|---|---|
| sahconnect → SystemAPI | Available | HTTP requests with an operator-provided API key. |
| sahconnect → adssh | Available | Launches the installed shell with your arguments. |
| sahapi → SystemAPI | Available | Three fixed GET proxies: fleet, alerts, and audit verification. |
| ComputeAPI → host enrollment | Planned | Automatic registration of newly provisioned capacity. |
| SystemAPI lease → adssh execution | Planned | Validated lease handoff; a frame lease_id alone grants no authority. |
| farmops scheduling | Early development | Catalog foundation exists; scheduler and runner are planned. |
Build on the parts that are ready.
Start with one tool or API. Follow the integration work as the lifecycle comes together.