Context Agent Sandboxes vs nono
Context Agent Sandboxes
context.ai
nono
nono.shSide by side
| Figure | Context Agent Sandboxes | nono |
|---|---|---|
| Price from | $20/mo | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| iOS | Yes | — |
| Android | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 7 | 0 |
| Spec score · Sandbox Software | 9.2 (#1) | 7.5 (#15) |
| Audit | Commands, files, connections, and permission decisions are recorded in an append-only audit log with the actor and decision maker. | Filesystem operations, network attempts, and command executions can be recorded in a SHA-256 Merkle-tree audit trail and exported as JSON. |
| Credential handling | Standing secrets are kept out of the sandbox; credentials are issued at the edge after authorization and expire with the action or run. | The site says credentials are injected at the boundary and never exposed to the agent. |
| Isolation | Sandboxes run as non-root container pods with capabilities dropped, a seccomp profile, and no cluster service-account token. | It uses Landlock on Linux and WSL2 and Seatbelt on macOS to enforce filesystem allow-lists that cannot be loosened after application. |
| Network controls | Administrators can choose open networking, a domain allowlist or workspace-only access, with outbound decisions logged. | It can block network access, allow specific domains, filter API endpoints, and route filtered traffic through an upstream proxy. |
| Purpose | Each agent task runs in its own sandbox on the customer's cluster under the permissions of the person who requested it. | nono is a kernel-enforced sandbox CLI and SDK for isolating AI agents, scripts, build tools, and other processes. |
| Support | Basic support through Context's standard channels during business hours is included in every agreement, with Enterprise support set per order. | The documentation links to GitHub for source code and issues and Discord for community support. |
Plans
Context Agent Sandboxes
- FreeFree
- FreeFree
- Plus$20 a month
- Plus$20 a month
- Pro$200 a month
- Pro$200 a month
- EnterprisePriced on request
In their own words
Context Agent Sandboxes
Context Agent Sandboxes gives each agent task a separate sandbox on the customer's cluster, using the permissions of the person who requested it. Each run begins in a fresh environment, which is destroyed after an idle period set to 30 minutes by default. Sandboxes run as non-root container pods with capabilities dropped, a seccomp profile, and no cluster service-account token. Administrators can choose open, domain-allowlist, or workspace-only network access, with allowlist decisions logged. In the supervised preset, commands require human approval and connections outside the allowlist prompt for a decision. Drive is not mounted: files pass through a permission-checking gateway, and outputs are pushed explicitly. Credentials are injected at the edge only after authorization. An append-only audit log records commands, files, connections, and permission decisions, including the actor and decision maker. Context lists more than 180 integrations across business categories, plus remote MCP servers. Enterprise sandboxes run on the customer's Kubernetes cluster, with KOTS installation options for EKS or AKS and an air-gapped bundle. Plans include Free at free, Plus at $20 a month, Pro at $200 a month, and custom-priced Enterprise.