> ## Documentation Index > Fetch the complete documentation index at: https://tesser.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Remote Development Host Vendors Research date: 2026-07-22. Devcloud needs organization-governed remote development hosts, not generic code-execution sandboxes. The compute must comfortably run 20 GB+ processes, retain a full mutable filesystem and package caches, expose long-running HTTP and WebSocket services, and behave like a remote Linux development machine. The practical vendor decision is whether Mintlify buys a workspace control plane for AWS or builds a thin one. AWS remains the likely compute provider in all cases. ## Coder Coder is the strongest fit and the first product to prototype. * The control plane is self-hosted in Mintlify infrastructure. * Terraform templates can provision full EC2 instances with arbitrary instance types, AMIs, EBS volumes, IAM, and VPC placement. * Coder's verified AWS templates preserve the full EC2 filesystem across stop/start. * The outbound workspace agent supplies routes, SSH, terminal access, port forwarding, lifecycle reporting, and application health. * Workspace applications provide authenticated path or wildcard-subdomain routes. * Workspaces can be shared with users or groups using separate use and administration permissions. * Prebuilt workspace pools, autostop, dormancy, audit, and richer RBAC are available, though several are Premium features. * The API and CLI cover lifecycle, execution, logs, routes, and workspace inspection. Primary sources: * [https://github.com/coder/coder](https://github.com/coder/coder) * [https://github.com/coder/coder/tree/main/examples/templates/aws-linux](https://github.com/coder/coder/tree/main/examples/templates/aws-linux) * [https://github.com/coder/coder/tree/main/examples/templates/aws-devcontainer](https://github.com/coder/coder/tree/main/examples/templates/aws-devcontainer) * [https://coder.com/docs/admin/templates/extending-templates/prebuilt-workspaces](https://coder.com/docs/admin/templates/extending-templates/prebuilt-workspaces) * [https://coder.com/docs/user-guides/shared-workspaces](https://coder.com/docs/user-guides/shared-workspaces) * [https://coder.com/docs/reference/api/workspaces](https://coder.com/docs/reference/api/workspaces) What Coder does not remove: * Mintlify must author the EC2/EBS template and component startup behavior. * Devcloud still needs its personal dashboard/client/backend route-selection layer; a Coder app route selects one workspace app, not a three-way mix. * Backend job ownership remains a Mintlify application concern. * Command-run log retention and Herdr attachment need validation or a small devcloud adapter. ## Ona Ona, formerly Gitpod, is the strongest managed alternative. * Ona operates the management plane while runners and isolated EC2 environments run in the customer's AWS VPC. * Environment classes support high-memory and custom Enterprise EC2 shapes. * The complete VM disk persists across stop/start. * Dev Containers, Docker-in-Docker, Docker Compose, `sudo`, long-running services, routed ports, environment commands, and logs are supported. * Enterprise prebuilds and EC2 warm pools reduce startup time. * The API can create an environment at an exact commit. * Organization roles, projects, runners, API/SDK access, PrivateLink, custom domains, and private registries are documented Enterprise capabilities. Primary sources: * [https://ona.com/docs/ona/runners/overview](https://ona.com/docs/ona/runners/overview) * [https://ona.com/docs/ona/runners/aws/environment-classes](https://ona.com/docs/ona/runners/aws/environment-classes) * [https://ona.com/docs/ona/environments/persistent-storage](https://ona.com/docs/ona/environments/persistent-storage) * [https://ona.com/docs/ona/projects/prebuilds](https://ona.com/docs/ona/projects/prebuilds) * [https://ona.com/docs/ona/projects/warm-pools](https://ona.com/docs/ona/projects/warm-pools) * [https://ona.com/docs/ona/integrations/ports](https://ona.com/docs/ona/integrations/ports) * [https://ona.com/api-reference/resources/environments/methods/create](https://ona.com/api-reference/resources/environments/methods/create) Important gaps: * The control plane remains vendor-operated. * Updating an existing environment to an exact commit is not a clear first-class CLI workflow; devcloud may still need to run Git and restart commands itself. * WebSocket behavior is not explicitly guaranteed in current port-routing docs. * Arbitrary detached execution with durable reconnectable logs is weaker than devcloud's required command-run contract. * Warm pools, custom AWS classes, APIs, and fine-grained governance require an Enterprise agreement with quote-only pricing. * Ona announced an agreement to join OpenAI in June 2026, making product and contract continuity a diligence item. ## Custom AWS A thin custom control plane on EC2 remains the fallback and may be the smallest solution for Mintlify's fixed three-component model. * EC2 provides unconstrained Linux and Docker behavior. * EBS preserves the checkout, package stores, build output, and local state. * Auto Scaling warm pools can retain stopped or hibernated prepared machines. * SSM supplies shell and command transport without public SSH. * An outbound devcloud agent can supply durable commands, logs, health, and routes without adopting a general workspace platform. The cost is owning provisioning reconciliation, agent upgrades, route auth, access control, idle cleanup, warm-pool claims, logs, and failure recovery. Coder should be treated as the reference implementation and buy-versus-build baseline for every one of those features. ## Harness CDE Harness CDE is the only additional vendor worth a sales call, not an immediate prototype. * Its hybrid model runs one Gitspace per VM in the customer's AWS account. * A Harness Delegate, VM Runner, and CDE Gateway handle lifecycle and routing. * Custom Ubuntu AMIs, Dev Containers, forwarded ports, IDE access, and autostop are supported. However, customer-hosted Gitspaces remain feature-gated, while public evidence for warm pools, programmable command/log APIs, shared environments, stable route identity, and WebSockets is incomplete. Primary sources: * [https://developer.harness.io/docs/cloud-development-environments/introduction/self-hosted](https://developer.harness.io/docs/cloud-development-environments/introduction/self-hosted) * [https://developer.harness.io/docs/cloud-development-environments/deep-dive-into-gitspaces/self-hosted-architecture](https://developer.harness.io/docs/cloud-development-environments/deep-dive-into-gitspaces/self-hosted-architecture) ## Excluded * Daytona, E2B, Cloudflare Sandbox, Vercel Sandbox, Modal, and Blacksmith Sandboxes solve generic sandbox or agent execution rather than the primary remote development host problem. * Blacksmith Testboxes were initially classified only as a test adjunct. Later protocol research showed they are live SSH hosts and therefore merit a narrow component-hosting experiment. (Protocol notes live in git history.) * DevZero's current product is Kubernetes optimization; its former development environment product is no longer publicly sold or documented. * DevPod OSS is client-only. Public DevPod Pro product, pricing, and support evidence is insufficient. * GitHub Codespaces runs only on GitHub-owned compute and does not provide the required shared environment or extensible control plane. * Okteto, OpenShift Dev Spaces, GitLab Workspaces, and similar products become relevant only if Mintlify first decides to make Kubernetes the box substrate. ## Recommendation Run the cheapest proof first on an owned **Blacksmith Testbox** using the official CLI and one explicit SSH local-forward experiment. If it cannot reliably host the components, run the same proof on **Coder Community Edition with persistent AWS EC2/EBS**. Request an Ona Enterprise architecture and pricing call only after those results. Build the custom AWS path only where Blacksmith fails and Coder proves heavier or less adaptable than devcloud's fixed component model.