Isolated execution for agent workloads.
Vagabond is an execution runtime that turns agent and automation work into isolated, auditable jobs — each run scoped to a tenant, a policy, and an explicit runtime boundary.
Built for work that cannot run on trust.
Vagabond separates what a job is allowed to do from where it runs, so operators can reason about each independently.
Isolation matched to the job
Workloads run in the boundary the work requires — from containers up to hardware-isolated virtual machines.
Tenant and policy scoping
Every job carries its tenant, its permissions, and its limits. Nothing executes with ambient authority.
Evidence that survives the run
Logs, artifacts, and results are recorded with provenance, so a finished job can always be inspected later.
From submitted job to recorded result.
Each stage has one responsibility, and the boundaries between them stay visible to the operator.
Submit
Work arrives as a typed job with a tenant, a policy, and declared inputs.
Isolate
The runtime places the job in an execution boundary sized to its risk.
Execute
Workers claim and run the job with narrow permissions and bounded resources.
Record
Outputs, logs, and artifacts land in durable storage with provenance attached.
Vagabond is in early access.
We are working with a small number of design partners running agent workloads that need real isolation. Tell us about your environment and what your jobs need to touch.