JDoodle

Best Self Hosted Alternatives to JDoodle

A curated collection of the 2 best self hosted alternatives to JDoodle.

Web-based compiler and IDE supporting many programming languages. Allows writing, running, and sharing code in a browser, with language/version selection, stdin support, and execution via public APIs and embeddable endpoints.

Alternatives List

#1
LiveCodes

LiveCodes

Open-source, browser-based code playground that runs entirely client-side; supports 90+ languages and embeddable demos, with Docker-based self-hosting.

LiveCodes screenshot

LiveCodes is a client-side code playground that runs entirely in the browser. It can be self-hosted on static file servers or CDNs, with a Docker-based setup to host additional services as needed.

Key Features

  • Client-side code playground that runs in the browser with 90+ languages/frameworks/processors
  • Embeddable in web pages via a lightweight SDK and simple embed options
  • No servers required for core functionality; standalone or embedded usage is supported
  • Import modules from npm, deno.land/x, jsr, GitHub and others
  • Developer-friendly embedding and deployment workflow, including a Docker-based self-hosting path
  • Comprehensive editor and tooling, including code formatting, intellisense, and optional AI assistance

Use Cases

  • Embed an interactive playground into documentation and tutorials for hands-on learning
  • Host private or internal coding environments without needing to manage back-end infrastructure
  • Standalone or embedded playgrounds for teams to experiment with multiple languages and frameworks

Limitations and Considerations

  • Some features rely on external services (e.g., short URLs, broadcast) and may not be available in purely static self-hosted deployments
  • If you require those services in a self-hosted setup, you can use the included docker setup to run compatible services
  • The core experience runs in the browser; certain advanced services may require additional hosting or configuration when self-hosted

Conclusion: LiveCodes provides a no-install, client-side playground with broad language support and an embeddable design, suitable for docs, tutorials, and in-app coding experiences. The project also offers Docker-based self-hosting for more control over services when needed.

1.3kstars
224forks
#2
XRSH

XRSH

XRSH is a browser-based XR terminal/REPL that can run standalone from a single executable, optionally booting a Linux ISO and embedding into A-Frame scenes.

XRSH screenshot

XRSH is a web-based XR terminal and REPL that runs in the browser and can be served locally or hosted as static assets. It is distributed as a single cross-platform executable that bundles the app and can optionally boot an emulated Linux ISO for a shell-like experience.

Key Features

  • Browser-first terminal/REPL interface designed for XR usage
  • Single-file distribution (a bundled executable that can be unpacked like a zip)
  • Multiple run modes: local server, container image, Nix-based installs, or hosted from a forge/pages setup
  • Optional ISO boot support and file overlay mechanism to customize content
  • Embeddable “isoterminal” component for A-Frame apps
  • Built-in help/manual access from within the terminal UI

Use Cases

  • Embedding an interactive terminal/REPL into WebXR or A-Frame experiences
  • Shipping a portable “terminal-in-a-browser” environment for demos, workshops, or kiosks
  • Hosting a customizable XR terminal endpoint from your own infrastructure

Limitations and Considerations

  • ISO-based mode can increase load times and may require additional WASM assets
  • Some deployment modes assume serving over HTTPS for full browser capabilities

XRSH is a pragmatic approach to distributing an XR-capable terminal experience as simple web content, while still allowing advanced setups such as ISO booting and environment customization. It fits projects that want an interactive terminal UI in the browser and the option to integrate it directly into WebXR scenes.

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