Agent Sandboxesagentsandboxes.org
Sandbox profile · Hosted platform

Control Plane Sandboxes

Answer in brief

Persistent, suspendable development sandboxes for coding agents inside a Control Plane "virtual cloud", with a browser IDE, SSH/VS Code/Cursor access and identity-based access to private services. A persistent dev-environment style sandbox for enterprises standardised on Control Plane, not a general-purpose SDK sandbox.

By the Agent Sandboxes editors · Updated

Overview

Control Plane is a multi-cloud "virtual cloud" platform that orchestrates hardened Kubernetes clusters across AWS, GCP, Azure, OCI and customer hardware. Its Sandboxes feature (a documented product with its own docs section and a cpln sandbox connect CLI command added in CLI v3.12.0, July 2026) gives AI coding agents "an isolated environment with persistent storage" inside your virtual cloud. You create one from the console by picking an image (templates, composed toolboxes or your own OCI image), a size and an app port; it is ready in roughly 60-90 seconds and exposes a browser IDE (code-server), a browser terminal (ttyd with tmux) and a public URL, or you connect from VS Code, Cursor or SSH.

The home directory lives on a persistent volumeset, so suspending a sandbox scales it to zero and bills only storage while keeping repos and credentials; resuming picks up where it left off. Private databases and APIs are reached through Control Plane's identity system rather than keys in the agent's context. Isolation is the platform's container isolation (cgroups, namespaces, seccomp-style syscall and capability restrictions); the docs do not name a microVM runtime. There is no sandbox SDK — control is via console and CLI — and no sandbox-specific pricing beyond the platform's per-millicore and per-megabyte rates. Control Plane reports SOC 2 Type II, PCI DSS Level 1, HIPAA and GDPR compliance.

Notable

  • cpln sandbox connect shipped in CLI v3.12.0 (3 July 2026); v3.13.0 switched SSH to a devuser account for de-rooted images.
  • Docs quote readiness in "~60–90 seconds" and suspend billing as "Storage only".
  • Platform compliance: SOC 2 Type II, PCI DSS Level 1, HIPAA, GDPR.

Control Plane Sandboxes specifications

AttributeDetails
IsolationContainer on Control Plane-managed Kubernetes (platform security docs: cgroups, namespaces, restricted syscalls and capabilities); the sandbox docs do not name a hypervisor or microVM runtime, although Control Plane blog posts refer to microVMs
DeploymentHosted platform · BYOC available · Self-hostable
Open sourceNo
SDKs and interfacesCLI
Cold start (vendor claim)Docs: a new sandbox "becomes ready in ~60–90 seconds"
Max session lengthNot documented
Persistence/root is mounted from a persistent volumeset, so repos, credentials, IDE settings and uncommitted changes survive suspend/resume and restarts; suspend scales the workload to zero (storage billed only); delete removes the volumeset
GPUNot documented for sandboxes; the platform sells GPU compute (T4 $0.35/hour to B200 $7.93/hour) for workloads
NetworkingEach sandbox has a password-protected browser IDE (/_ide/), browser terminal (/_term/) and a shareable public app URL (default port 8080); reaches private services via Universal Cloud Identity and Cloud Wormhole so "the agent never handles a key"
PricingNo sandbox-specific rates; platform usage pricing is $0.06205654 per millicore-month vCPU, $0.00706330 per MB-month memory, General Purpose SSD $0.21224989 per GB-month, egress $0.12/GB; suspended sandboxes bill storage only
Free tierNot documented
ComplianceSOC 2 Type II, PCI DSS Level 1, HIPAA and GDPR compliant (per docs)
RegionsAny location a GVC (Global Virtual Cloud) spans: AWS, GCP, Azure, OCI regions, other clouds, or your own Kubernetes clusters (BYOK)

Facts from Control Plane Sandboxes’s public documentation, verified November 9, 2026. Performance numbers are vendor claims.

Strengths and trade-offs

Strengths

  • You already run on Control Plane and want agent workspaces with identity-based access to private services
  • You need persistent, suspendable environments with IDE, terminal and SSH access
  • You want the sandbox to run in your own clouds or Kubernetes clusters under one control plane

Trade-offs

  • No programmatic sandbox SDK (console and CLI only); creation is a console workflow in the docs
  • Isolation runtime beneath the container layer is not documented
  • Startup of 60-90 seconds is far slower than microVM sandboxes
  • No dedicated pricing, limits or idle-timeout documentation

Good fit for: Enterprises on Control Plane that want long-lived agent dev environments with identity-based access to their private infrastructure.

How Control Plane Sandboxes compares

SandboxIsolationOpen sourceSelf-host / BYOCCold start (vendor)Max sessionSnapshots / pauseGPUSDKs
Control Plane SandboxesContainer (runtime not named)NoYes / Yes60-90 sNot documentedNot documented / YesNot documentedCLI
Northflank SandboxesCloud Hypervisor microVMNoNo / Yes<1 sUnlimitedNot documented / YesYesJavaScript/TypeScript, Python
Koyeb SandboxesMicroVMNoNo / Not documentedNot documentedUp to 24 hNot documented / Not documentedYesPython, JavaScript/TypeScript
Railway SandboxesLinux VMNoNo / NoNot documentedNo cap (idle 30 min default)Yes / NoNot documentedJavaScript/TypeScript, CLI, GraphQL API
CoderTemplate-defined (VM/pod/container)YesYes / NoNot documentedNot documentedNot documented / YesNot documentedCLI, REST API, MCP server
Ona (formerly Gitpod)Dedicated cloud VMNoNo / YesNot documentedNot documentedNot documented / YesYesPython, JavaScript/TypeScript, Go, CLI, REST API
GitHub CodespacesDedicated VM per codespaceNoNo / NoNot documented12 h, 30 min idleNo / YesNoCLI, REST API

See all Control Plane Sandboxes alternatives →

Frequently asked questions

What is Control Plane Sandboxes?
Persistent, suspendable development sandboxes for coding agents inside a Control Plane "virtual cloud", with a browser IDE, SSH/VS Code/Cursor access and identity-based access to private services. A persistent dev-environment style sandbox for enterprises standardised on Control Plane, not a general-purpose SDK sandbox.
How does Control Plane Sandboxes isolate code?
Control Plane Sandboxes documents its isolation as: Container on Control Plane-managed Kubernetes (platform security docs: cgroups, namespaces, restricted syscalls and capabilities); the sandbox docs do not name a hypervisor or microVM runtime, although Control Plane blog posts refer to microVMs.
Is Control Plane Sandboxes open source?
No, Control Plane Sandboxes is not open source. It does offer a bring-your-own-cloud deployment.
How much does Control Plane Sandboxes cost?
No sandbox-specific rates; platform usage pricing is $0.06205654 per millicore-month vCPU, $0.00706330 per MB-month memory, General Purpose SSD $0.21224989 per GB-month, egress $0.12/GB; suspended sandboxes bill storage only Check the official pricing page for current rates.
What are the alternatives to Control Plane Sandboxes?

Sources

  1. controlplane.com/platform/ai-agents
  2. controlplane.com/pricing
  3. docs.controlplane.com/whatis
  4. docs.controlplane.com/guides/sandbox/getting-started
  5. docs.controlplane.com/guides/sandbox/container-internals
  6. docs.controlplane.com/cli-reference/release-notes
  7. docs.controlplane.com/core/security

Cite this page

Agent Sandboxes. (2026). Control Plane Sandboxes. agentsandboxes.org. Last reviewed November 9, 2026. https://agentsandboxes.org/sandboxes/control-plane-sandboxes/

Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.