What is an isolated agent environment?
An isolated agent environment is a dedicated runtime where one agent executes with its own files, tools, packages, browser state, secrets, and network controls, without sharing that mutable surface with unrelated workloads.
Why It Matters
Agents need more than logical separation
For real agent workloads, isolation is not just about process separation. It is about containing mutability. The moment a run can install packages, write files, log into websites, or handle sensitive inputs, the environment boundary becomes part of the product.
Browser sessions stay scoped to one agent
Browser automation produces stateful sessions, cookies, downloads, and screenshots that should stay scoped to a single environment.
Package installs compound without boundaries
Package installs and temporary files alter the runtime over time. That mutability stays manageable only when the environment boundary is clear.
Security controls belong at the agent level
Secrets and outbound network access should be agent-level controls, not an afterthought bolted onto a generic worker pool.
State persists with one agent identity
Persistent state and snapshots are easier to reason about when one environment maps to one agent identity.
Sandbox Vocabulary
Sandbox language is useful, but incomplete
Sandbox is a useful starting term because it points to isolated code execution. Spinup uses the term isolated agent environment when the runtime also needs persistence, tools, state, and agent-level controls.
Sandbox names the boundary
Most teams already use sandbox for isolated code execution, which makes it a natural starting point.
Environment names the operating model
Spinup adds files, packages, browsers, secrets, and network policy around one agent, not just a disposable execution slot.
The distinction matters in practice
Once state, controls, and snapshots live with the agent, the runtime does more than sandbox a single run.
Isolated Environments in the Spinup Runtime
From sandbox language to a complete environment model
The goal is not just safe code execution. It is one persistent environment per agent, with clear controls for state, secrets, network policy, and snapshots.
Early Access
See if Spinup fits your runtime stack
Join the early-access waitlist if this is the runtime shape your team has been missing.