CodeSandbox

Best Self Hosted Alternatives to CodeSandbox

A curated collection of the 5 best self hosted alternatives to CodeSandbox.

CodeSandbox is a cloud-based IDE for web development that lets users create, edit, and preview JavaScript/TypeScript apps (React, Vue, Angular, Node) instantly. It offers templates, real-time collaboration, GitHub integration, and deployment tools.

Alternatives List

#1
code-server

code-server

Self-hosted VS Code in a browser with remote development, extensions, and secure access—ideal for cloud/dev containers, labs, and consistent dev environments.

code-server screenshot

code-server is an open-source project by Coder that runs Visual Studio Code in the browser, letting you develop on a remote machine while using a familiar VS Code interface. It’s designed for remote development, enabling consistent environments and access from any device via a web URL.

Key Features

  • Browser-based VS Code experience backed by a server-side environment
  • Supports installing and running many VS Code extensions (Open VSX marketplace support)
  • Built-in authentication options and the ability to run behind a reverse proxy for HTTPS
  • Terminal access inside the IDE for running builds, tests, and CLI tooling on the host
  • Settings sync-like portability via dotfiles/config management approaches (bring-your-own config)
  • Multiple installation options (standalone binary, Docker) and Linux-first deployments

Use Cases

  • Remote development on a workstation, VM, or homelab server from low-power devices
  • Standardized dev environments for teams, classrooms, or workshops
  • Securely accessing project code and tooling without copying source to a local machine

Limitations and Considerations

  • Some VS Code extensions—especially those tightly coupled to Microsoft services/marketplace—may not work as expected
  • Requires careful security hardening when exposed to the internet (auth, TLS, network controls)

code-server is a practical way to centralize development environments while keeping the editing experience close to desktop VS Code. It works well for remote-first workflows, disposable environments, and scenarios where you want tooling to run near compute resources.

75.7kstars
6.4kforks
View Details
#2
Puter

Puter

A self-hostable personal cloud that provides a web-based desktop, file storage, apps, and multi-user access in the browser.

Puter screenshot

Puter is a self-hostable “personal cloud” that runs as a web-based desktop environment in the browser. It combines a file manager, app launcher, and user accounts to provide a lightweight, desktop-like experience for accessing files and web apps from anywhere.

Key Features

  • Browser-based desktop UI with windows, launcher, and desktop-like workflows
  • File manager with upload/download and folder organization
  • Multi-user support with accounts and user home directories
  • App model for running/installing web apps inside the desktop environment
  • Web access from any device without a native client

Use Cases

  • Personal or family private cloud for browsing and organizing files via a familiar desktop UI
  • Lightweight “web OS” portal for hosting internal tools as apps for a small team
  • Kiosk/remote workstation experience where users only need a browser

Limitations and Considerations

  • Desktop-like UX is best suited to light productivity and web apps; it is not a full VM/remote desktop replacement
  • Feature set and APIs may change as the project evolves; review release notes before upgrades

Puter is a good fit when you want a simple, browser-first desktop experience on top of your own storage and services. It’s especially useful as a unified entry point for files and lightweight web applications under a familiar UI paradigm.

38.5kstars
3.4kforks
View Details
#3
Coder

Coder

Open-source platform to provision secure, reproducible cloud workspaces from code using Terraform, with web access and IDE support.

Coder screenshot

Coder is an open-source platform for creating and managing remote development workspaces on your own infrastructure (Kubernetes, VMs, or cloud instances). It provisions reproducible dev environments from code, centralizes access, and helps teams secure and standardize developer setups while keeping source code and data in controlled networks.

Key Features

  • Workspaces defined as code using Terraform templates for repeatable, auditable environments
  • Workspace lifecycle management (create/start/stop/delete) with per-developer or per-project configurations
  • Browser-based access plus IDE integrations (e.g., VS Code via remote/SSH-style connectivity)
  • Secure connectivity model for reaching private networks without exposing developer machines
  • Role-based access control and audit/logging capabilities for enterprise governance needs
  • Extensible provisioning with environment variables, parameters, and template versioning
  • Supports running workspaces on Kubernetes or traditional compute (depending on template/provider)

Use Cases

  • Standardize dev environments across a team and reduce “works on my machine” issues
  • Provide secure contractor or student workspaces that run inside a private network
  • Spin up ephemeral, cost-controlled environments for feature branches or onboarding

Limitations and Considerations

  • Requires Terraform knowledge to build and maintain high-quality templates
  • Operational complexity can be non-trivial (networking, identity, and compute orchestration)

Coder is best suited for organizations that want developer environments managed as infrastructure with stronger security and reproducibility than local setups. It fits well where teams need consistent tooling, centralized control, and scalable workspace provisioning across multiple infrastructure targets.

11.9kstars
1.1kforks
View Details
#4
Sandstorm

Sandstorm

Self-hosted platform for running web apps with per-user sandboxes, easy install, app store packaging, and sharing via secure links and access controls.

Sandstorm screenshot

Sandstorm is a self-hosted “personal cloud” platform that lets you install and run multiple web applications on your own server with strong isolation between apps and users. It provides an app-market style workflow, integrated identity/sharing, and a capability-based security model so apps can be safely shared and accessed.

Key Features

  • One-command install and web-based admin for managing users, apps, backups, and updates
  • App installation via Sandstorm “apps” (packaged as Cap’n Proto/SPK bundles) with an app market concept
  • Per-app/per-user isolation (each document/workspace runs in its own sandbox) to limit data access between apps
  • Capability-based security and sharing: share specific documents/apps using granular permissions and unguessable links
  • Built-in identity and access management with multiple login providers (e.g., email/password and OAuth-based providers)
  • Reverse-proxy style routing and HTTPS support (typically deployed behind a TLS terminator)
  • Integrated email notifications and background tasks support for apps (app-dependent)
  • Backup/restore tooling for app data (grain backups) and server migration support

Use Cases

  • Host a private suite of collaboration apps (notes, wikis, chats, file tools) with consistent login and sharing
  • Provide a secure multi-user environment for small teams to run web apps without giving them full server access
  • Run “single-document” app instances (e.g., one shared pad/wiki doc) that can be shared by link with permissions

Limitations and Considerations

  • Project activity has historically slowed compared to peak years; verify current maintenance status and security updates before production use.
  • Sandstorm relies on its own packaging/runtime model; not all generic Docker/web apps can be installed without a Sandstorm-specific package.

Sandstorm is best suited for users who want an integrated, security-focused way to host multiple web apps with simple sharing and strong isolation. If you value per-document sandboxes and capability-based sharing over generic container hosting, it provides a distinctive approach to self-managed web apps.

7kstars
709forks
View Details
#5
Livebook

Livebook

Livebook is a collaborative, web-based notebook for running Elixir code, building data workflows, and deploying notebooks as interactive apps, with real-time collaboration.

Livebook screenshot

Livebook is a web application for authoring and running interactive notebooks backed by the Elixir runtime. It combines executable code cells with rich text, visuals, and integrations to support data exploration, automation, and reproducible computational documents. Notebooks can be shared, collaborated on in real time, and turned into interactive “apps” for non-developers.

Key Features

  • Interactive notebooks with Elixir code cells, Markdown, and rich outputs (tables, charts, etc.)
  • Real-time multi-user collaboration with presence and synchronized editing
  • Runtime management: connect local, remote, and clustered runtimes; attach to running nodes
  • Package/dependency management inside notebooks (Mix-based) and reusable “Smart cells”
  • Integrations for data work (e.g., Kino-based visual components; common I/O and visualization patterns)
  • Secrets management and environment-based configuration for notebooks/apps
  • Export/share options (notebook files, links/sharing, and runnable artifacts depending on setup)
  • Deploy notebooks as Livebook Apps with interactive inputs and controlled execution

Use Cases

  • Data exploration, ETL prototyping, and reproducible analysis in Elixir
  • Team runbooks and operational notebooks for debugging/observability workflows
  • Internal tools: ship a notebook as an interactive app for stakeholders

Limitations and Considerations

  • Primarily optimized for the Elixir ecosystem; other languages require external bridging
  • Some features (collaboration/deployments) may depend on specific runtime/network configuration

Livebook is well-suited for teams that want notebooks with strong concurrency and distribution primitives from BEAM/Elixir. It bridges documentation and execution, making it practical both for exploratory work and for operationalizing notebooks as interactive applications.

5.7kstars
483forks
View Details

Why choose an open source alternative?

  • •Data ownership: Keep your data on your own servers
  • •No vendor lock-in: Freedom to switch or modify at any time
  • •Cost savings: Reduce or eliminate subscription fees
  • •Transparency: Audit the code and know exactly what's running