
About This Playground
Want to try a security tool, inspect some network traffic, or work through an authorized lab without installing Kali Linux on your laptop?
iximiuz Labs' Kali Linux playground gives you a fresh Linux server prepared for information security experiments. It starts in seconds, opens in your browser, and provides root access to a familiar Kali environment where you can install the exact assessment, analysis, and troubleshooting tools your task requires.
This is a real VM, not a restricted container or an online command shell. The playground has its own kernel, root filesystem, network interface, and init system, so packet capture, service inspection, firewall experiments, and other low-level Linux tasks work much like they would on a regular remote server.
Use the Kali playground for learning security tools, participating in CTFs and intentionally vulnerable labs, analyzing files and network captures, testing your own services, and practicing defensive investigation. Explore HTTP, TLS, DNS, authentication, and Linux permissions; examine open ports and running processes; or reproduce a security finding in an isolated machine before touching a real environment.
Because the VM is disposable, you can install a pile of specialized packages, change system configuration, generate test certificates, or run an unfamiliar proof of concept without leaving the resulting mess on your primary system. When the experiment is over, destroy the playground and start again from a clean state.
Use security tools only against systems you own, the playgrounds provided for the exercise, or targets for which you have explicit authorization. Scanning, probing, exploiting, or disrupting third-party systems is prohibited—even if the tool makes it easy. The playground is also not intended for production workloads, sensitive data, or long-running services.
For everything else, start the VM and investigate. Capture the packets, inspect the service, trace the request, understand the weakness, and learn how to fix it. Security skills are best developed hands-on—but always inside a clearly authorized boundary.
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 →