Node.js Playground
The latest Node.js, NVM, Docker, VS Code, and a bunch of extensions.
About This Playground
Want to try an npm package, explore an unfamiliar JavaScript project, or build a small web application without filling your laptop with another node_modules directory?
iximiuz Labs' Node.js playground gives you a fresh Linux development machine with the latest Node.js, NVM, Docker, and VS Code with a useful collection of extensions. It starts in seconds and opens in your browser, so you can clone a repository, install its dependencies, and start coding almost immediately.
This is not a limited online JavaScript sandbox. The playground is a lightweight but fully fledged Linux VM running on iximiuz Labs' bare-metal infrastructure. You get a real shell, root access, a complete filesystem, and the freedom to install system packages, start background services, open network ports, or inspect the operating system underneath your application.
Use the Node.js playground for learning JavaScript or TypeScript, experimenting with npm packages, testing installation instructions, exploring GitHub projects, and building short-lived development or demo environments. Switch Node.js versions with NVM, use npm or your preferred package manager, run tests and development servers, attach the debugger, or try a framework without leaving its toolchain behind on your own machine.
The included Docker Engine makes it easy to containerize your application or start supporting services such as PostgreSQL, Redis, or RabbitMQ alongside it. If you build a website, API, dashboard, or WebSocket server, expose its port to get a generated HTTPS URL for yourself or to share with someone else.
iximiuz Labs playgrounds are not intended for production workloads or services that must stay online indefinitely. Playground sessions have a time limit, public URLs should not be treated as production endpoints, and disposable environments are the wrong home for secrets, sensitive data, or the only copy of your source code. Commit important work to Git or preserve the playground before ending the session.
For everything else, open the IDE or terminal and start coding. Install the enormous dependency tree, switch runtimes, break the build, fix the build, and finally turn that tiny script into a containerized service. If the experiment gets messy, a clean Node.js machine is only a restart away.
Happy hacking!
A real VM, not a container
Get root on a VM with its own kernel, so Docker, Kubernetes, and systemd just work.
Read the docs →
SSH from browser or CLI
Use the built-in web terminal, or connect with labctl ssh, plain ssh, scp, or rsync.
Read the docs →
Drive it with AI
Let Claude, Codex, or any MCP client start this playground and run commands in it.
Read the docs →
Expose HTTP(S) ports
Give any web app running inside the VM a public URL - for yourself or to share with others.
Read the docs →
Share terminals
Invite others into your terminal session, or open it yourself from another device.
Read the docs →
Customize with init scripts
Add shell scripts that run at boot to install packages, clone repos, or seed test data.
Read the docs →
Private networking
VMs reach the internet via NAT with no public IP; several VMs share bridge networks.
Read the docs →
Ephemeral or persistent
By default, VMs are destroyed when the session ends; enable persistence to keep the disks for next time.
Read the docs →
Built-in container registry
A private registry.iximiuz.com for every playground to share images across services and VMs.
Read the docs →