[ why hotwash ]
Most ranges do one thing. This one fights back.
Jeopardy platforms hand every team the same flag. Cyber ranges run a canned adversary against you. Hotwash seeds a different, verified instance per team, grades blue as rigorously as red, and puts both cells in the same live match — then writes the debrief.
// seeded & verified
Uncopyable, never broken
Each team’s seed produces its own artifacts and flags, and an independent solver recovers every flag before an instance is served. Leaks are worthless and traceable; 2 a.m. “the flag’s broken” messages don’t happen.
// live red // blue
Outcomes, not keystrokes
A mediation plane sits between both cells and scores what they actually achieve — a seeded proof you can’t read without real compromise, real detections, real eviction, real uptime. Not scripted buttons.
// the payoff
Every fight ends in a hotwash
The after-action report writes itself from the engagement journal: five hotwash questions, per-operator scorecards, the timeline, and a prioritized fix plan with an owner for each gap.
// side by side
What you get that you usually don’t.
| Capability | Hotwash | Jeopardy CTF platforms | Cyber ranges & labs |
|---|---|---|---|
| Per-team seeded, uncopyable instancesEvery team gets its own hosts, creds and flags. A leaked flag is wrong for everyone else. | ✓ | — | partial |
| Every instance verified before it is servedAn independent solver re-solves each team’s instance first. Broken challenges never ship. | ✓ | — | — |
| A shared flag names the leakerThe integrity log ties a copied flag back to the team it belonged to. | ✓ | — | — |
| Graded blue-team detectionSubmit a Sigma / YARA / Suricata-style rule; it runs on planted malicious plus benign data. Pass with zero false positives. | ✓ | — | partial |
| Live red-vs-blue in one matchBoth cells on one board at once. Scored on outcomes the mediation plane can see — not on keystrokes or a canned script. | ✓ | — | partial |
| Pre-game loadout draftA budgeted draft of real capabilities before kick-off, so no two matches open the same way. | ✓ | — | — |
| Broadcast observer boardBranching attack map, crown-jewel status, momentum and a key-moments reel built for the room. | ✓ | partial | partial |
| Automatic facilitated hotwashThe five hotwash questions, per-side and per-operator scorecards, the full timeline and an owned fix plan — written from the match journal. | ✓ | — | partial |
| Multi-team cohortsOne organizer action moves every team from prep to live together, each on its own seeded variant, ranked on one leaderboard. | ✓ | partial | — |
| Offline and air-gappedTargets, consoles and scoring run with the cable unplugged; content ships as signed bundles. | ✓ | partial | — |
| Own-kit / digital twinTeams work from their real offensive and defensive stack against container- or VM-backed infrastructure, telemetry into their own SIEM. | ✓ | — | partial |
| Classroom grade passbackRostered classes over LTI 1.3, per-student seeded variants, scores to the gradebook. | ✓ | partial | partial |
| Author once, fight manyOne scenario in the DSL yields a different verified instance per team, in all three modes. | ✓ | — | — |
✓ built inpartial possible with add-ons, plugins or manual work— not typical of the category
Columns describe common platform categories generically, not any specific vendor. Features and tiers change; check a product’s current documentation before you buy.
// see it, don’t take our word
Watch a match. Then run one.
The observer board is live on the site — three scenarios, three outcomes. When you’re ready, every tier runs on the same seeded engine.