Solutions
Solutions
The same control plane serves three kinds of user. Here is what each gets from it.
For platform and DevOps teams
Keep one record of what ships, where it runs and what it may use.
- Applications with Quotas per Cluster, Namespaces and Ownership links
- Pipeline runs, Deployments and Commit statuses in one place
- Jail and Delete protection as controls on the record
For teams building with agents
Run agents under the same access rules and audit as everything else.
- Agents with a chosen Runtime and an explicit list of MCP servers
- Processes with sequential, concurrent, handoff or supervisor Topologies
- Approval gates that wait for a person, with mobile push
For CI and automation
Report delivery and drive work from scripts with a scoped machine identity.
- Service accounts with a wl_ PAT and the ci:agent Machine role
- An OpenAPI document to generate clients from
- Idempotent Invoke with an Idempotency-Key header