About This Playground
Want to try a Linux command, test an RPM package, or reproduce a RHEL-family server issue without provisioning a cloud VM?
iximiuz Labs' Rocky Linux playground gives you a fresh, vanilla Rocky Linux server with root access and a familiar enterprise Linux environment. It starts in seconds, opens in your browser, and behaves like a regular remote machine: install packages with DNF, inspect RPMs, manage services with systemd, configure users and networking, compile software, and change almost anything you like.
This is a real VM, not a container pretending to be a server. The playground has its own kernel, root filesystem, network interface, and init system, so low-level Linux tools and server-side software work as expected. You can install Podman, Docker, Kubernetes, a database, or an entire application stack—much like you would on a VPS, a cloud instance, or a machine in your homelab.
Use the Rocky Linux playground for learning RHEL-style system administration, testing shell scripts and configuration changes, troubleshooting packages and services, building RPM-based software, and running short-lived development or demo environments. Its compatibility with the RHEL ecosystem makes it particularly handy for checking deployment instructions, testing Ansible roles, reproducing enterprise Linux issues, or adapting a setup originally written for RHEL, CentOS, AlmaLinux, or another related distribution.
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 anything irreplaceable.
For everything else, start the VM and get your hands dirty. Break a systemd unit, add the wrong repository, turn the RPM database into a small disaster—then destroy the machine and start fresh. That's what playgrounds are for.
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 →