CubeSandbox gives every AI agent its own hardware-isolated MicroVM with a dedicated Linux kernel — not a shared-kernel container but a true KVM virtual machine — booting in under 60ms with less than 5MB of memory overhead per instance, enabling thousands of concurrent sandboxes on a single server via kernel sharing and Copy-on-Write memory. The Rust-built CubeProxy exposes an E2B SDK-compatible REST API on Axum, so existing E2B Cloud applications switch by changing one environment variable with zero client code changes. CubeMaster orchestrates cluster-level scheduling in Go while Cubelet manages node-local sandbox lifecycles including create, run, pause, resume, snapshot, and destroy operations. CubeVS, the eBPF-powered network layer, enforces per-sandbox isolation with LPM trie-based egress policies entirely in kernel space — no userspace context switches — while CubeEgress provides an L7 security proxy with per-domain, per-path, and per-method allowlists plus automatic credential injection that keeps secrets invisible to sandbox code. Hundred-millisecond-granularity snapshots enable checkpoint, rollback, and parallel fork from any saved state. The volume framework supports E2B-compatible pluggable storage with independent lifecycle and cross-sandbox sharing. Production deployment uses Terraform on Tencent Cloud or Helm charts on Kubernetes, K3s, or TKE, with full ARM64 support alongside x86_64 and AutoPause/AutoResume for cost optimization. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Describe an app in one sentence and sandboxd, a self-hosted AI app builder, has a coding agent build it in an isolated sandbox and hand back a live preview URL. Start from a blank prompt, a React, Next.js, Express, or FastAPI starter, or an imported public Git repo. Refine it in one persistent chat beside Preview, Code, Terminal, and Git tabs. Pick OpenCode, Pi, or Claude Code. Point OpenCode or Pi at local or remote OpenAI-compatible and Anthropic-compatible endpoints, LiteLLM gateways included. A proxy injects provider keys on the wire, so nothing secret lands in a sandbox. Did the agent get it wrong? Every task is checkpointed first, so one click reverts the turn. Snapshots, forks, and named versions keep known-good points to branch from. Edit files in the browser, review file-by-file diffs, commit, and push. Secrets are write-only and encrypted per app. Idle sandboxes sleep and wake on the next request. One modest server can host per-user previews, coding playgrounds, or an agent platform. The app library installs 80+ curated open-source apps, such as Ghost, n8n, Gitea, and Grafana, each in its own sandbox. Every console action is also a /v1 HTTP call with an OpenAPI spec. Upgrades back up the database, health-check the new version, and roll back on failure. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

OpenAgentCore puts Codex, Claude Code, and MiniMax Code behind one self-hosted Agents API, so your applications start agent sessions through the official OpenAI SDK while the work runs on machines you control. Set OPENAI_BASE_URL to your installation and issue a Project API key, and the same client code that talks to OpenAI now talks to your Core. Each session runs a native harness, exactly as it runs on a developer's machine, with the model provider, model ID, and protocol you configure per harness or per session. Choose where sessions execute: microsandbox nodes you operate, Docker, E2B, or a self-hosted workstation, VM, or container connected by the oac-daemon with a credential scoped to one environment. Idle microsandbox sessions release their compute and resume on a compatible node with workspace files intact, so long investigations do not rent a machine while they sleep. The Web console walks operators through setup, tracks sessions and turns, manages models and credentials, and issues keys, while the separate Core API serves operators and the Agents API serves applications. Durable execution state in PostgreSQL keeps events, results, and schedules recoverable across restarts. Sandbox providers, workspace filesystems, harnesses, and model providers all plug in through defined protocols, so every layer can be replaced on its own. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 14,000 GitHub stars and enterprise adoption by security-conscious organizations, Coder transforms how development teams provision, manage, and secure their coding environments. Every workspace is defined as a Terraform template, meaning infrastructure engineers can standardize development environments across EC2 instances, Kubernetes pods, Docker containers, or any combination, while developers get self-service provisioning that launches in seconds rather than days of manual setup. The WireGuard-based networking layer establishes encrypted tunnels between developer machines and remote workspaces, providing low-latency access without exposing ports or configuring VPN concentrators. Automatic idle detection shuts down unused workspaces after configurable periods, directly reducing cloud compute costs for organizations running hundreds of developer environments. The Coder Agents feature introduces native AI coding capabilities where the agent loop executes entirely within the control plane on self-hosted infrastructure, keeping LLM API credentials out of individual workspaces and eliminating credential exfiltration risks. Centralized model governance allows platform teams to approve specific AI providers and models, set per-user spend limits, and maintain complete audit logs of all prompts, tool calls, and agent activity. IDE integration supports VS Code through a dedicated extension, JetBrains IDEs via Gateway and Toolbox plugins, and browser-based code-server for web access. The template registry provides pre-built configurations for common development stacks. DevContainer support builds environments from standard devcontainer.json specifications. Deploy on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

AgentBox is a self-hosted browser workspace that runs Claude Code and Codex CLI on a server you control, so a task goes from chat to reviewed code without leaving one place. Open a workspace from an empty project, an uploaded archive, or a Git clone, then talk to the agent in streaming web chat or drop into its original interactive terminal when you want the CLI itself. Files persist between sessions along with your home configuration and chat history, so a project picked up on a laptop continues on a phone exactly where it stopped. Review per-file diffs line by line before committing, pushing, or opening a pull request, and download the result when no Git connection is configured. Shared files, layered home templates, Claude skills, and MCP configuration carry your setup into every new workspace, with per-workspace overrides when a project differs. A trusted team shares central account pools with per-user scopes, while every model request is recorded with tokens, cache hit rate, cost, and latency, exportable to CSV and optionally capped by credits. An optional tunnel reaches allowlisted repositories and databases on private networks, and six interface styles with light and dark modes keep long sessions comfortable. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

With 2,400+ GitHub stars, HolyClaude replaces a two-hour manual setup process with a single docker compose up command that launches a fully configured AI coding workstation. The container ships with Claude Code pre-installed alongside seven additional AI CLIs — Gemini CLI, OpenAI Codex, Cursor, TaskMaster AI, Junie, OpenCode with OpenRouter multi-provider support, and Pi Coding Agent — all accessible through the CloudCLI browser-based web interface on port 3001. A headless Chromium browser running on Xvfb display :99 comes pre-configured with Playwright 1.61 for automated screenshots, testing, and web scraping without additional setup. The development toolchain includes Node.js 26, Python 3, TypeScript, git, GitHub CLI, database clients for PostgreSQL, SQLite, and Redis, plus deployment CLIs for Vercel, Wrangler, Netlify, and Azure. Process management uses s6-overlay for automatic restarts and graceful shutdown, while bind mounts to ./data/claude and ./workspace ensure credentials, configuration, and project files persist across container rebuilds. The full image supports AMD64 and ARM64 architectures, running on Linux, macOS with Docker Desktop, Windows with WSL2, and Synology or QNAP NAS hardware. A slim tag at roughly 2GB omits the browser stack for environments that do not need it, while the full image at 4GB includes everything. Users authenticate with their existing Anthropic account directly through Claude Code with no credential relay or proxy involved. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Try an idea in React, Svelte, Python, or SQL without installing anything: LiveCodes is a browser-based playground where code compiles, runs, and previews the moment you type it. Starter templates open ready-made projects for most of the 90+ supported technologies. The desktop editor brings completion, multi-cursor editing, Emmet, and Vim or Emacs bindings, while a lighter touch-friendly editor takes over on phones and tablets. Packages from npm, deno.land/x, jsr, and GitHub import straight into your code, and a console, compiled-code viewer, and test runner show what happens behind the preview. Bring projects in from GitHub gists, GitLab snippets, JS Bin, or zip files, then share them as links or QR codes, export them as HTML, JSON, or zip archives, or send them to CodePen and JSFiddle. Deploy a project to a public URL on GitHub Pages, sync your work across devices, or broadcast your editor and result live to a classroom. An embed builder and SDKs for JavaScript, React, Vue, Svelte, Solid, Preact, and web components place playgrounds inside documentation pages, and prefilled code makes every example editable. Projects stay private by default. Local assets, snippets, themes, and dark or light modes tailor the workspace to each person. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With 83,000+ GitHub stars and $18.8M in Series A funding, OpenHands delivers the leading open-source platform for AI coding agents that scored 68.4% on SWE-bench Verified with Claude Opus 4.6, outperforming Devin 2.0's publicly reported 45.8%. The Agent Canvas web UI organizes work into persistent conversations where agents edit files, run shell commands, browse the web, and execute multi-step development tasks inside isolated Docker sandbox containers. The observe-plan-act loop drives agent behavior: the Python controller manages LLM abstraction via LiteLLM routing to 100+ providers including OpenAI, Anthropic, Google, DeepSeek, Qwen, Llama, and local Ollama models. Built-in skills for code review, Docker management, PRD generation, repo-rules enforcement, release notes, and test running attach to conversations automatically via auto-discovery or trigger-based activation. The Automations system schedules recurring agent tasks with configurable templates for CI workflows, dependency updates, and documentation generation. MCP server integration enables agents to access external tools and data sources. The REST API powers an OpenAI-compatible endpoint for connecting agents to chat UIs, IDEs, and voice platforms. GitHub, GitLab, Slack, and Jira integrations enable pull request reviews, issue resolution, and team notifications. The SDK provides Python and REST APIs for embedding agents in custom tools with local or cloud execution, custom agent behaviors, and Kubernetes deployment. On RepoCloud, deploy OpenHands on a dedicated VPS with Docker socket access, persistent project storage, root SSH access, and complete control over your AI development infrastructure, all under the MIT license.

Zeabur is a self-hosted web platform that deploys and runs your services on your own Kubernetes cluster, presenting the cluster as simple projects and services instead of raw manifests. Every change starts as a readable plan listing the exact fields it will write and who owns them today, and nothing is applied until you confirm it. When something breaks, Zeabur says so in plain words and points at the fix: a worker that restarted fourteen times gets a button straight to the logs from the run before the restart. You deploy from Git repositories, from an uploaded folder or ZIP archive, or directly in the dashboard, then follow live logs, open a terminal inside a container, and watch CPU and memory move over time. Projects are namespaces and all state lives in Kubernetes objects, so there is no Zeabur database to back up, and uninstalling the platform leaves your Deployments, Services, and Ingresses running untouched. Companion pieces add passkey sign-in for kubectl with tokens that expire in minutes, image builds from Git through a BuildKit operator, and a catalog of cluster components and app templates. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Scatter a few cheap VPS boxes, a home server, and one bare metal machine across three different providers, and Uncloud still treats them as a single place to run your applications. You describe services in ordinary Docker Compose files, deploy them with the uc command line tool, and publish any container port as a public HTTPS endpoint in a single command. Every machine joins an encrypted WireGuard mesh with its own container IP addresses, so services on different continents reach each other directly without VPN configuration or exposed ports. A built-in DNS server resolves service names to container IPs, and the integrated Caddy reverse proxy provisions and renews Let's Encrypt certificates automatically, sharing them across the cluster. Rolling updates replace containers with zero downtime, persistent Docker volumes keep stateful services safe, and the Unregistry integration pushes image layers straight to your machines when no registry is available. There is no control plane to babysit: each machine keeps a synchronised copy of the cluster state, and SSH access to any single node is enough to manage the whole fleet. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Stateful serverless actors that run indefinitely, sleep when idle, and persist state across restarts without external database round trips. Rivet provides a vendor-neutral alternative to Cloudflare Durable Objects, delivering long-running processes with co-located in-memory state and per-actor SQLite databases on any infrastructure you choose. The Rust engine comprises four packages: Pegboard for actor orchestration, Gasoline for durable execution, Guard for traffic routing via Envoy, and Epoxy implementing multi-region KV storage through EPaxos consensus. Each actor maintains instant-access in-memory state plus a dedicated SQLite database for relational queries, backed by RocksDB on single nodes or PostgreSQL with NATS pub/sub for multi-node clusters. RivetKit SDKs in TypeScript, Rust, and Python support built-in WebSocket connections, task queues, scheduling, and CRDT-based real-time collaboration. The v2.3 rewrite moved the core runtime from JavaScript to native Rust via WebAssembly, eliminating main-thread blocking across Node.js, Bun, Deno, and Cloudflare Workers. A built-in dashboard provides actor inspection with real-time Prometheus metrics. Deploys as a single Docker container on port 6420 with optional PostgreSQL for persistence. Available on RepoCloud with a dedicated VPS under the Apache 2.0 license.

Open Compute is a self-hosted Cloudflare Workers-compatible platform that runs your Workers, storage, and AI services on hardware you own, from one binary and one daemon. Deploy the Worker code you already wrote with its config file and framework adapters, then roll back to an earlier immutable deployment when a release misbehaves. Serve traffic locally or over HTTPS through the shared Gateway, with routes you control instead of a vendor account. Each instance stays isolated with its own data directory and credentials, while you switch between registered instances from the same operator view. Bindings cover the platform pieces applications actually need: key-value data, SQL databases, object storage, stateful objects, queues, durable multi-step workflows, scheduled cron, cache, vector search, and AI search. Logs and a live tail show what running Workers are doing right now, and health, backup, and recovery workflows keep a single machine manageable without a cluster. Verified upgrades roll back automatically when something fails, and object bytes can move to S3-compatible storage when local disk is no longer enough. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

One server, treated properly: Nanocl runs your containers and full virtual machines from a single declarative Statefile, reconciling what is running against what the file says, so a lone host gets cluster discipline without cluster ceremony. Containers group into Cargoes with replica counts, ordered init containers, and health-aware restarts; finite jobs run to completion and stop. When a workload needs a real kernel or a custom disk image, it boots as a QEMU virtual machine beside the containers instead of forcing a second platform. Publishing is built in: the proxy controller terminates TLS and routes HTTP and TCP traffic, and the DNS controller keeps service names resolving while workloads come and go. Secrets for registries, certificates, and environment variables attach where they are used, never inside the file itself. The daily loop is a CLI and an API: list processes, follow logs, exec into a container, watch events, and back up the entire deployment state before you change it. Namespaces keep projects apart on the same host, and Statefile arguments, templates, and sub-states carry one definition from staging to production. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT or Apache-2.0 licensed.