Delegate the running. Keep the owning.
A sandbox is a Docker container on your own laptop, desktop or VPS. Put it on a server, hand it end-to-end operation — and because the platform sits off the command path, you give up none of the control.
- No codethe platform never stores your source, your prompts or your credentials
- MITall of intentic is open source, platform included
- No portsnothing inbound is opened; the tunnel dials out
It runs on hardware you own
The sandbox dials out over a private Cloudflare tunnel and your browser talks to that address. Put the machine on a VPS and it keeps working without you — the platform never relays a file, a keystroke or a credential.
Chat, files, editor, terminal
Sandboxes, repos, credentials, capabilities
Identity + sandbox URL only. Off the command path.
The image is a file you approve
Everything past the base image is an overlay Dockerfile. The agent can propose a line and then waits: you read the diff and approve before a rebuild applies it.
The bill is measured where it is spent
Every turn's tokens and cost land in the sandbox's own ledger, by day, provider and model. It is your subscription, so the platform never meters it.
What the platform actually holds
Identity, the sandbox's URL, and the grants that let a teammate reach it. Not your code, not your keys, not your transcripts.
Stays inside your sandbox
- Your code and repos
- Every credential and token
- The agent's transcripts
- The container and its image
All the platform holds
- Your identity (Google sign-in)
- The sandbox's name and URL
- Billing state
- Grants to invited teammates
What it stores is AES-256-GCM encrypted, with no decrypt path in the product.
One sandbox, several people
The owner installs the tools; invited teammates share that same sandbox, each signed in as themselves. Setup stays owner-gated.
- Invite by email; grants are enforced by the daemon, fail-closed.
- Teammates chat, drive and review, and mirror the sandbox's ports.
- Revoking or leaving takes effect the moment you press it.