Secure sandboxes
for AI agents.
You can YOLO it. Use --dangerously-skip-permissions.
# Install the CLI$ curl https://islo.dev/install.sh | bash# Log in once$ islo login# Run Claude Code in a sandbox$ islo run claude✓ Syncing ./src → remote sandbox✓ Claude Code connected✓ Policies loaded (strict mode)❯ fix the auth bug in login.tsTry to break out
Click any attack to watch it get blocked in real-time.
Customize your policies
Define what your agents can do. Enforce it at every level.
Filesystem
System-level enforcement at the kernel - not a whitelist of commands.
allow /workspace/** rwx-deny /etc/** ----deny /.env ----Built on proven infrastructure
Real isolation enforced at the kernel level, with extra policies for safety.
Kata Containers on bare metal
Hardware-virtualized containers running on bare metal cloud infrastructure. Dedicated kernels, true isolation - not just namespaces.
eBPF syscall filtering
Policies enforced at the kernel level via eBPF. Not a wrapper, not a shim - actual syscall interception before execution.
L3 network policies
Egress control at the network layer. Allowlist domains or IPs - everything else is dropped at the socket.
Secrets never mounted
Secrets are injected at runtime via secure channels. They never exist on the filesystem - agents can't read what isn't there.
Persistent filesystems
Full ext4 filesystem per sandbox. Your data persists between runs - no weird FUSE edge cases or NFS quirks.
Dynamic resources
Sandboxes scale up to 8 CPUs and 16GB RAM on demand. Pay only for what you use - billing from cgroup metrics.
Know when something's wrong
Detect unusual patterns and suggest policies before they become problems.
Filesystem access blocked
2 min agoread /etc/passwdNetwork request blocked
5 min agocurl https://prod-db.internal:5432High file access rate
8 min ago47 files in /src/auth/ in 3 secondsConsider secrets policy
12 min agoAgent reading .env files frequentlyPay only for what you use
We only bill for actual CPU cycles, resident memory, and consumed storage.
CPU Time
Measured from Linux cgroup CPU usage counters (cpu.stat usage_usec). Billed with a minimum of 6.25% CPU utilization per second of runtime.
Cumulative CPU usage
Memory Time
Measured by sampling Linux cgroup memory usage (memory.current). Billed with a minimum of 0.25 GB per second of runtime.
Actual memory usage
Storage Time
Measured hourly by summing actual size of objects in your environment's storage bucket.
Storage usage in GB-hours
Get started in under a minute
Install the CLI, create a sandbox, run your agent.
curl https://islo.dev/install.sh | bash