The vault for agents
Sandboxed agents get exactly the access their job needs, and never see a secret.
curl -fsSL onecli.sh/install | shBacked byY Combinator
SOC 2 Type IIWorks with the sandboxes, vaults and agents you already run
Keys stay in the vault.
Access goes out the door.
- 1
The agent calls out from its sandbox
Authorization: Bearer {{GITHUB_TOKEN}}
- 2
The gateway checks the policy and adds the key
policy qa-permissions allowed Bearer ghp_7Qz2••••••••dRt
- 3
The API answers. The agent never saw the key
200 OK { "login": "acme-bot" }
One vault. Every agent.
Never in the prompt.
Never in the logs.
Keys stay in the gateway and are added on the way out. A leaked sandbox leaks nothing.
A policy per job
Each agent gets the systems and actions its job needs.
Built for sandboxes
E2B, Daytona, Docker, and the like.
Connect a tool, hand out no token
Jira, GitHub, Slack and 100+ more, all through the gateway.
Every call on record
Which agent, which policy, what happened.
Open source
Self-host it in one container, or use the cloud.
Give your agents access,
not your keys


