Agents get full control inside their sandbox and reach only what you allow outside it. prokube Agent Sandboxes, preconfigured and operated by us.
Use cases
Claude Code, Codex, opencode or any other coding agent can run with full permissions in a sandbox, without reaching your databases or API keys. Developers connect from the browser or from their own tools.
Your agents get programmatic access to short-lived sandboxes through the Python SDK or MCP. Creating, suspending and resuming one usually takes under a second, and suspended sandboxes use no CPU or memory.
Why sandboxes
On a laptop, an agent has the developer's access and keys, even inside a container. With a hosted sandbox service, your code and data end up on someone else's servers. A sandbox on your own cluster avoids both.
Agent incidents and sources from our talkWhat you get
Sandboxes are part of prokube AgentOps. We install them on your infrastructure and work out the network rules with your security team. After that, we run them.
On-premises, in a private cloud, with a sovereign hosting provider or air-gapped. The snapshots are stored on your cluster too.
Your admins decide which hosts sandboxes can reach and which API keys they get. They can see every sandbox in every workspace.
We install updates and monitor capacity. Support with agreed response times is part of the contract.
Setup usually takes less than a day. Then we hold a workshop with your team and build the first use case together.
For developers
There is a Python SDK, a CLI called pk and an MCP server. In our tests, a new sandbox answered its first command after about half a second.
from prokube.sandbox import SandboxClientwith SandboxClient() as client:client.create("analysis")client.write_files("analysis", {"/workspace/sales.csv": sales_csv,"/workspace/report.py": report_py, # written by your agent})client.run("analysis", "python3 -m venv .venv && "".venv/bin/pip install pandas matplotlib")result = client.run("analysis", ".venv/bin/python report.py")print(result.stdout)chart = client.read_file("analysis", "/workspace/chart.png")client.delete("analysis")
Create a sandbox from a preset and run commands in it. Commands run as root, so the agent can install whatever it needs. Files go in with write_files and come back with read_file.
The UI
Screenshots from the dashboard and from the tools developers connect with.
The sandboxes of a workspace with their state and preset.

Under the hood
All parts are open source, and you get the source code of prokube's own parts as well. If we ever part ways, the sandboxes keep running.

Your cluster, or one we set up for you. Sandboxes run on its worker nodes.
kubernetes.ioStarts sandboxes, saves them as snapshots and restores them.
github.com
Isolates sandboxes from the host kernel with a kernel that runs in user space.
gvisor.dev
Alternatively runs sandboxes as micro-VMs with their own guest kernel, on Cloud Hypervisor.
katacontainers.ioAll outbound traffic goes through it. It blocks hosts that are not on the allowlist and adds API keys on the way out, so the keys are never inside a sandbox.
agentgateway.dev
Login and roles. Whoever can edit a workspace can use its sandboxes.
keycloak.orgStores the snapshots on your cluster.
github.comThe dashboard, the Python SDK, the pk CLI and the MCP server. Also the service that turns workspace roles and network rules into sandbox policies.
We set up a test cluster for your team and go through it with you.
Source-available. Engineered in Germany. No vendor lock-in. Ever.