Helmsman · Roadmap
Define an agent once. Govern it on any cloud.
Cloud agents are moving out of pilots and into production — and each cloud governs only its own. Helmsman is extending its agent control plane across AWS and Azure so one permission model, one approval flow, one audit trail, and one spend cap hold across both.
one governance model — two clouds
The idea
Governance is the part no cloud sells across both.
AWS governs agents on AWS. Azure governs agents on Azure. Neither governs across the other. For a team running work on both, that means two permission models to keep in sync, two audit trails to reconcile, and two places a runaway agent can spend before anyone notices. Helmsman’s answer is to make the governance neutral: define and permission an agent once, and let it run wherever it needs to — without the controls changing shape per cloud.
The agent is portable. So is the way you govern it.
What the cross-cloud plane is built to do
One definition, either cloud
Describe an agent once — its permissions, its model, the tools it may use. Change a single field to move that same definition from AWS to Azure. The spec does not fork per cloud.
One audit trail across both
Every invocation is recorded the same way — who ran it, what it cost, which tools it touched — whichever cloud executed it. The trail lives with Helmsman, not scattered across two vendors’ consoles.
Human approval, anywhere it runs
Multi-agent processes pause at the gates you define and wait for a person. Approve or reject from the dashboard or your phone, whether the step ran on AWS or Azure.
Tools stay governed at the boundary
An agent only ever reaches the tools you granted it — enforced by Helmsman as each call is made, not left to the runtime in the cloud. Credentials stay with the control plane and never travel to the workload.
Spend caps that refuse, not report
A per-organization ceiling that turns the next invocation away when it would cross the line — a control that stops spend, not a number you reconcile after the bill arrives.
Helmsman already runs agents, multi-agent processes, and human approval gates today, under one org-scoped audit model. Cross-cloud is the next layer — built the way the rest of the control plane was: one governed capability at a time, proven before it ships, with the enforcement point inside Helmsman rather than the cloud it runs on.