Control Plane Sandboxes vs Ona (formerly Gitpod)
Choose Control Plane Sandboxes for enterprises on Control Plane that want long-lived agent dev environments with identity-based access to their private infrastructure; choose Ona (formerly Gitpod) for enterprises that want VM-isolated, Dev Container-based environments for developers and background agents inside their own AWS or GCP VPC. Control Plane Sandboxes uses Kata microVM (per vendor blog) isolation; Ona (formerly Gitpod) uses Dedicated cloud VM isolation.
Key differences between Control Plane Sandboxes and Ona (formerly Gitpod)
- Isolation: Control Plane Sandboxes uses Kata microVM (per vendor blog); Ona (formerly Gitpod) uses Dedicated cloud VM.
- Self-hosting: Control Plane Sandboxes documents a self-hosted option; Ona (formerly Gitpod) does not.
- Company headquarters: Control Plane is based in United States; Ona is based in Kiel, Germany.
- SDKs and interfaces: Only Ona (formerly Gitpod) lists Python, JavaScript/TypeScript, Go and REST API.
What they have in common
- Both are hosted platforms.
- Neither is open source.
- Both can pause and resume a sandbox.
- Both list CLI.
Control Plane Sandboxes vs Ona (formerly Gitpod) at a glance
| Attribute | Control Plane Sandboxes | Ona (formerly Gitpod) |
|---|---|---|
| What it is | 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. | Enterprise cloud development environments provisioned as isolated VMs (EC2 or Compute Engine) in your own VPC from a Dev Container config, with SDKs, a CLI and Codex-based background agents; hosted Ona Cloud was retired on 31 October 2026. |
| Type | Hosted platform | Hosted platform |
| Isolation | 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 a Control Plane blog post of 26 October 2026 says sandboxes run in dedicated Kata Containers microVMs | Each environment is "an isolated VM with dedicated compute, storage, and networking" — an EC2 instance on AWS runners or a Compute Engine instance on GCP runners — created from a Dev Container configuration; runners live in your VPC and the Ona-hosted management plane never sees source code or secrets |
| Open source | No | No |
| Self-host / BYOC | Yes / Yes | No / Yes |
| SDKs | CLI | Python, JavaScript/TypeScript, Go, CLI, REST API |
| Cold start (vendor claim) | Docs: a new sandbox "becomes ready in ~60–90 seconds" | Not documented |
| Max session | Not documented | Auto-stop after a configurable inactivity timeout (--inactivity-timeout); no fixed maximum published |
| 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 | Stop an environment "to preserve its state" and start it again; delete removes it permanently; environment classes set instance type and disk (default classes from m6i.large with 45 GB up to g5.4xlarge with 300 GB); warm pools (Enterprise) |
| Snapshots / pause | Not documented / Yes | Not documented / Yes |
| GPU | Not documented for sandboxes; the platform sells GPU compute (T4 $0.35/hour to B200 $7.93/hour) for workloads | Default AWS environment classes include GPU classes on g5.4xlarge instances with 300 GB disk |
| Networking | Each 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" | Environments run in your VPC; subnets can stay private with outbound through NAT or proxy; "kernel-level policy enforcement" and scoped credentials advertised as guardrails |
| Pricing | Sandbox-specific rates are not published; 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 | Contact sales (Enterprise); Ona Cloud, whose usage-based Core tier started at $20/month, was shut down on 31 October 2026 |
| Free tier | Not documented | Not documented |
| Compliance | SOC 2 Type II, PCI DSS Level 1, HIPAA and GDPR compliant (per docs) | SOC 2 and GDPR logos with a trust portal at trust.ona.com; details not specified on the pages read |
| Regions | Any location a GVC (Global Virtual Cloud) spans: AWS, GCP, Azure, OCI regions, other clouds, or your own Kubernetes clusters (BYOK) | Wherever you deploy runners: any AWS or GCP region in your own account |
| Company headquarters | California, United States | Kiel, Schleswig-Holstein, Germany |
| Good fit for | Enterprises on Control Plane that want long-lived agent dev environments with identity-based access to their private infrastructure | Enterprises that want VM-isolated, Dev Container-based environments for developers and background agents inside their own AWS or GCP VPC |
Verified November 14, 2026 from each provider’s documentation. Cold-start figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Control Plane Sandboxes
- 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
Reasons to choose Ona (formerly Gitpod)
- You need dedicated-VM environments that never leave your own AWS or GCP account
- You want Dev Container-defined, reproducible workspaces for both developers and background agents
- You are an enterprise standardising on Codex-based background agents with audit and policy controls
Trade-offs to check first
- Control Plane Sandboxes: A sandbox SDK is not documented; the sandbox docs describe creation through the console and connection through the CLI
- Control Plane Sandboxes: The sandbox docs do not name the isolation runtime; a Control Plane blog post says Kata Containers microVMs
- Ona (formerly Gitpod): Hosted Ona Cloud is no longer available; remaining use is on runners in your own AWS or GCP account, with pricing via contact sales
- Ona (formerly Gitpod): The documented built-in agent is the Codex Agent; the earlier Ona Agent is no longer listed in the docs
Both are worth piloting with your own image and region. See the full Control Plane Sandboxes profile and Ona (formerly Gitpod) profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Control Plane Sandboxes or Ona (formerly Gitpod) better for AI agents?
What is the difference between Control Plane Sandboxes and Ona (formerly Gitpod)?
Which is open source, Control Plane Sandboxes or Ona (formerly Gitpod)?
How do Control Plane Sandboxes and Ona (formerly Gitpod) isolate code?
How does Control Plane Sandboxes pricing compare with Ona (formerly Gitpod)?
Do Control Plane Sandboxes and Ona (formerly Gitpod) support GPUs?
Can you self-host Control Plane Sandboxes or Ona (formerly Gitpod)?
How long can sessions run on Control Plane Sandboxes and Ona (formerly Gitpod)?
--inactivity-timeout); no fixed maximum published.Do Control Plane Sandboxes and Ona (formerly Gitpod) support snapshots or pause and resume?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 14, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
Agent Sandboxes. (2026). Control Plane Sandboxes vs Ona (formerly Gitpod). agentsandboxes.org. Last reviewed November 14, 2026. https://agentsandboxes.org/compare/control-plane-sandboxes-vs-ona-gitpod/