enzarb
Agentic development sandboxes on your own Kubernetes cluster.
Every project gets a pod with a real terminal and a Claude agent. It runs on your cluster, behind a syscall boundary, holding none of your GitHub credentials.
Continue with GitHubA sandbox, not a chat box
Every project boots a pod with a real terminal and a Claude agent speaking ACP. It edits files, runs your test suite and reads the output in the same place you do.
Kubernetes all the way down
Projects and Environments are CRDs. An operator reconciles them into sandbox pods, routes and a Postgres cluster it manages for you — on your cluster, not ours.
A syscall boundary, on by default
Sandboxes run under gVisor. Tenant code talks to runsc rather than your node's kernel, so isolation is the runtime's job and not a flag someone has to remember.
No GitHub credential in the sandbox
git and gh reach GitHub through a credential-injecting egress proxy that adds the token on the way past. A compromised agent has nothing portable to steal.
Preview environments
Deploy an Environment and it comes up on its own hostname under your environment domain, ready to hand to somebody else.
Runs while you are away
Issue, pull request and push events from the GitHub App start agent runs on their own. Come back to a branch and a pull request.