Built for Ubuntu & Windows

Give every AI agent
its own isolated environment.

Let your agents work. Keep the boundaries.
Disposable environments with isolated desktops, a separate host identity, and policy-controlled network access.

Get AgentSilo Read the docs

Rootless containers. Deliberate permissions. Your control.

An agent's own environment, layer by layer Three glowing glass layers represent the agent runtime, identity and network policy, and disposable workspace. This is a conceptual illustration, not a security boundary diagram.

Isolated environments

A workspace of their own.

Controlled access

You set the network policy.

Disposable by design

Create, run, and tear down.

Purpose-built boundaries

Room to work.
Boundaries that matter.

The environment your agents need, with explicit control over what they can reach.

A dedicated runtime

Each silo has a rootless container, Chromium desktop, browser profile, and work directory. Keep agent work separate from your own.

Rootless Podman containers

A separate host identity

Silos run under the unprivileged agentsilo host identity. Your home, browser sessions, and privileged sockets stay out of the silo.

Separation from your operator account

Deliberate network access

Per-silo policies route traffic through an identity relay and proxy. Allow, deny, or ask for approval, with every decision audited.

Fail-closed network egress
From install to first silo

A clear path
to getting started.

Download and install the Ubuntu host package, then run the documented action sequence. Open the desktop client to create your first silo.

On Windows? The desktop app manages a WSL2 Ubuntu environment for your silos.

Follow the installation guide
Ubuntu 26.04 · after package installation
# 1. Check host prerequisites
sudo agentsilo-install host-prerequisites

# 2. Build the silo images
sudo agentsilo-install images

# 3. Apply the egress firewall policy
sudo agentsilo-install egress --force

# 4. Verify the installation
sudo agentsilo-install verify
The egress --force step applies firewall rules. Review the full guide ↗
Your workflow, contained

Built for the work agents do.

Run coding agents and browser workloads with an environment you can inspect, control, and dispose of.

01 / CODE

A workspace for coding agents

Give Pi or Codex its own work directory and terminal. Attach directly to the agent through the desktop operator UI.

02 / BROWSE

A separate browser desktop

Work with a silo's Chromium desktop through the noVNC viewer. Browser profiles stay separate from your personal sessions.

03 / OPERATE

Manage the full lifecycle

Create, start, attach, recover, restart, and purge. Manage silo state and network approvals from one operator interface.

How it works

A deliberate path from agent to internet.

You manage the lifecycle. Each silo's outbound traffic passes through identity and policy controls.

  1. 01 / OPERATOR

    Desktop app

    Manage silos, attach to desktops, and review approvals.

  2. 02 / RUNTIME

    AgentSilo workspace

    A narrow workspace API and disposable rootless containers.

  3. 03 / EGRESS

    Identity & policy

    Relay, proxy, and per-silo policy control outbound access.

Security, honestly stated

Know your boundaries.

AgentSilo is defence in depth. It relies on your host kernel and a separate unprivileged host identity; a container is not an independent VM boundary. Treat anything typed into a silo browser as agent-visible.

Read the security model