Regulated and security-sensitive deployments
Composing under containers and microVMs
Layer agentvfs inside container or microVM isolation for regulated workloads, keeping the vault, forks, and policy boundary while the kernel enforces containment.
The problem
Some workloads need kernel-level containment guarantees against hostile processes — something a top-level command boundary alone cannot provide.
How agentvfs helps
Because agentvfs draws one clean line, it composes under OS isolation. Run it inside a container, microVM, or seccomp profile: you keep vaults, forks, checkpoints, and structured results while the kernel enforces the hard boundary.
What that looks like in practice
- ▸agentvfs is honest that it is not a syscall monitor — it layers rather than replaces.
- ▸The workspace runtime and the isolation layer stay cleanly separated.
- ▸Structured ExecutionEnvelopes give an audit trail suitable for compliance review.
- ▸Bounded execution with SIGTERM-then-SIGKILL escalation caps runaway commands.
Try it on this workflow
See the architecture, more use cases, or the guides.