Ship code you can trust
Agents verify their own work like a human would - click through the browser, run migrations, and hit real services, not just unit tests and lint.
Everything coding agents need.
Persistent, secure infrastructure that is connected to your entire organization, so you can run AI agents easily and securely.
Use cases
What teams run on Islo.
Triage while you sleep
Agents pick up tickets from Linear or Jira, investigate, and open PRs - running around the clock.
Sandboxed execution, real capabilities
Run user plugins, code interpreters, or agent-generated scripts in isolation - without touching your production.
$ islo use --agent codex
✓ Computer ready in 280ms
✓ Codex running inside the computer
✓ Databases, browsers & dev servers on localhost
~$ codex "fix the failing webhook tests"13:58gateway · egress
01
Credentials go out, not in
The agent uses a placeholder. The gateway swaps in the real key on the way out - so secrets are never exposed.
agent
stripe.charges.retrieve(...)$STRIPE_SECRET_KEY · placeholder only
islo gateway
Authorization: Bearer $STRIPE_SECRET_KEY→Authorization: Bearer sk_live_••••••••••••4f2a
injected at egress · per-request audit
stripe api
200 OK · charge_XYZkey never touched computer memory
02
Responses come back trimmed
Big API payloads are summarized before they reach the agent - less data exposed, fewer tokens burned.
→ GET api.github.com/repos/billing/pulls/4821
← 200 OK · 847 KB body received
✓ trimmed to summary · 1.2 KB → agent context
03
Risky requests get blocked
Requests that leak secrets or hit banned destinations are stopped before they leave.
→ POST api.unknown-host.com/upload
body: customers.csv · contains sk_live_…
✗ blocked · matched deny: exfiltration
13:46computer · running stack
swift-lantern · servicesreal Linux VM. not docker-in-docker. all on localhost.
postgres:5432
up·4h 11m
redis:6379
up·4h 11m
api (fastapi):8000
up·4h 10m
worker
up·4h 10m
web (next):3000
up·4h 08m
stripe-mock:12111
up·4h 11m
18:20session · resumed
~ · you@laptopwoken · 1.2s
$ islo use swift-lantern ✓ computer resumed · 4h 12m uptime · disk warm ✓ services restored · postgres redis api worker web stripe-mock ✓ vault re-bound · no keys written · audit chain continues working dir ~/work/billing (git: eng-2043-stripe-v2, 2 unstaged) open files lib/stripe_auth.py · routes/charge.py · PLAN.md agent state step 8 of 8 · paused on human approval last action drafted PR #4821 (14:03) waiting on merge call for stripe_v2_enabled agent › Welcome back. Ready when you are.
Same filesystem. Same history. Same context.
pricingprovisioned · per hour
CPU time
$0.07/CPU-hour
billed on provisioned cores while the env is running
memory time
$0.04/GB-hour
request 2 GB, pay for 2 GB while it runs
storage time
$0.0007/GB-hour
billed on provisioned disk
overnight agent session (8 hours)
CPU · 2 cores × 8h$1.12
Memory · 4 GB × 8h$1.28
Storage · 10 GB × 8h$0.06
Total$2.46
monthly team (5 devs, ~4h/day)
CPU · 800 CPU-hours$56.00
Memory · 1,600 GB-hours$64.00
Storage · 8,000 GB-hours$5.60
Total~$126/mo
$50 in free credits on signup · no card required