Four lines. Governed agent. Running.
Minimal governed agent
Start building: first Control Plane extension — or build visually.
What scaffolding removes
Without HUMΛN-shaped infrastructure, you re-implement auth sprawl, delegation, audit logging, policy enforcement, routing, error surfaces, and provenance chains. With HUMΛN, those concerns are protocol behavior — you focus on domain logic and tests.
Three ways to build
Visual builder
Compose steps, gates, and deploy without a spec war.
Marketplace
Install governed bundles; fork and extend with receipts intact.
CLI: one command, full project shape
Five-minute quickstart
Follow the guided path — environment, bundle manifest, first deploy — in the docs. The promise is minutes-to-running, not days-to-boilerplate.
Open the quickstart →Marketplace as distribution
Build → test → publish → governed listing → users install with policy inheritance. Revenue share and publisher rules live with the Marketplace team — start from the publisher path when you are ready to ship broadly.
Enterprise pull path
Developers prototype → teams standardize → governance requirements surface → enterprise procurement buys infrastructure, not shadow IT. HUMΛN is designed for that bottom-up honesty instead of fighting it.
Enterprise overview →Operational surfaces (Control Plane)
Proof of depth — not a toy SDK. These are live routes in the Console.
| Surface | What you get | Open |
|---|---|---|
| Extensions Hub | Installed extensions — managed, versioned, active. | See installed extensions |
| Developer dashboard | Publisher KPIs, assets, install analytics. | Open developer dashboard |
| Webhooks | Wire HUMΛN events into your stack. | Manage webhooks |
| Executions | Live and historical workflow runs. | View executions |
| Agents | Deployed agents — status, versions, health. | Manage agents |
Deployment options
What you can rely on
- Human sovereignty — identity and consent stay oriented to the person, not the vendor dashboard narrative.
- Verifiability — receipts and provenance are first-class, not an afterthought log stream.
- Neutral protocol — model and cloud choices stay swappable; HUMΛN does not trap you in a single provider story.
- Open standards posture — integrate through documented contracts (HTTP APIs, manifests, OAuth patterns) instead of proprietary-only SDK lock-in.