Phoenix / Forge
Test infrastructure · cyber range

Phoenix Forge

Rehearse on a copy, not on production.

Can we try it first? Forge is the test infrastructure under Phoenix. You draw a network in the browser — firewalls, switches, routers, servers, a SIEM, an attacker — and Forge builds it as real, isolated containers on your own host, cabled and addressed exactly as drawn. It's where Crucible can attack before it touches production, where Nest can be watched catching it, and where your team can test a firewall change or a detection rule without risking anything real.

lab runs onyour host · isolated containers
Why a lab

Production is the wrong place to find out.

Changes need a dress rehearsal

A new firewall rule, a new segment, a new sensor: on a copy of the network, a mistake costs a redeploy. In production, it costs an outage.

Detection has to see an attack to prove itself

A rule that never fired proves nothing. In the lab, an attacker node runs real attack traffic so you can check what your SIEM actually catches.

Analysts learn on real traffic

Every device is a working system with real packets on the wire — not a slideshow. Training and incident drills use the same tools your SOC uses every day.

How a lab is built

From drawing to running network in five steps.

Every step is automated, and a redeploy is safe to run again — no manual fixes afterwards.

1 · Design

Draw the topology

Drag devices onto the canvas and cable them together. Each device carries its interfaces, addresses and role.

2 · Render

Turn it into a lab definition

Each device type maps to a container image. Forge writes the lab definition and deploys it with containerlab on your host over SSH.

3 · Configure

Devices come up already working

Once the links are wired, each device runs its own setup: the firewall loads its nftables zones and routes, the switch builds its bridge, the attacker starts its attack loop.

4 · Address

IPs set from the host, then checked

Forge assigns addresses from the host side, so even minimal images with no shell get theirs — then reads them back to verify.

5 · Reconcile

Safe to run again

Forge works out which addresses share a network segment and which device is its gateway, and keeps the running lab in line with the design on every redeploy.

Why containers

Fast, repeatable, disposable

Labs are built from plain Linux containers. They start in seconds, keep their configuration, and can be torn down and rebuilt identically — unlike nested VMs.

  Browser  — topology editor
        │  REST / WebSocket
        ▼
  Forge backend  — labs · devices · consoles · capture · Proxmox
        │  SSH
        ▼
  Lab host  — one container per device, wired with virtual links
        │
        ▼
  Monitoring  — Prometheus · Grafana · Loki (packet capture)
Example

A typical SOC lab.

Three zones behind one firewall — the shape of a real company network, small enough to rebuild in minutes.

ZoneSubnetWhat it does
INTERNAL10.10.10.0/24Office network; the firewall is its .1 gateway
DMZ10.10.20.0/24Public-facing services; blocked from INTERNAL in both directions
SIEM10.10.30.0/24Wazuh; reachable from both zones
Working in the lab

Every device one click away.

Consoles & web UIs

Terminals and device web interfaces open through SSH tunnels — the Wazuh dashboard over HTTPS, Windows over RDP.

Packet capture

Traffic is captured and streamed to Loki, and you read it on a ready-made Grafana dashboard.

Proxmox VMs

VMs tagged as lab machines appear in the sidebar with start/stop controls and an embedded console.

Device palette

What you can put in a lab

Linux host Firewall (nftables) L2 switch FRR router Attacker Wazuh SIEM OWASP Juice Shop Windows · Ubuntu · Android VM — slower

Container devices are preferred. Full VMs still work by running QEMU inside a container, but they boot more slowly.

Status

What works today, and what we're finishing.

Topology editor → running lab — available Automatic addressing & safe redeploy — available Consoles, packet capture, Proxmox — available UI showing the exact live interfaces & addresses — in progress External Wazuh container data link — in progress
Get started

Build a copy of your network and break it safely.