An identical box per team
Root inside, the same services for everyone, on one host dedicated to your event and destroyed when it ends. Nothing is shared with another customer.

Simulate real-world cyberattacks, defend critical services, and compete in real time.
A course can show a team an exploit. Only an opponent shows whether they can stop one while keeping the service up.
One learner, one target, no opponent.
Every team attacks every other team's box while defending its own, live.
Defence is a slide, not a decision made under pressure.
Patch, filter and restore while the checker keeps scoring your service every tick.
A score with no record of how it was earned.
Per-tick scoring, with an export that explains every point after the event.
Shared infrastructure running someone else's content.
A host dedicated to your event, running the services and checkers you choose.
A one-off that cannot be repeated.
Snapshots, restores and a reusable setup, run again for the next cohort.
Every 60 to 300 seconds the same loop runs for every team, and the tick is scored the moment it ends.
Check. The checker plants a fresh flag in every team's service and reads earlier ones back.
What the platform does once the network opens, and why each part matters to the team running the exercise.
Root inside, the same services for everyone, on one host dedicated to your event and destroyed when it ends. Nothing is shared with another customer.
A service is a container image on any stack, and its checker speaks the service's own protocol. Import checkers written for ctf-gameserver, Hackerdom checksystem, ForcAD or enochecker3.
Checks arrive from rotating addresses in the players' range. Filtering is judged per port, with the evidence kept, so a penalty can be explained to the team that received it.
SLA, defence and attack per flag store every tick, from a model derived from ECSC 2023, with weights you set and freeze when the network opens.
A wrecked box returns to its snapshot in one action. An outage of the host or the checker runner pauses the game, so nobody is scored down for it.
A farm-ready submission endpoint, attack info as JSON every tick, personal WireGuard access, and a Discord bot that answers with the scoreboard.
Every team plays attacker and defender at once. The exploits you write are the exploits you have to stop, under the same clock.
Three ways to build the exercise, from an event your team runs on its own services to a scenario we design around your organization.
Register the vulnerable services your team should learn to defend, with their source published to players once the network opens.
Bring checkers and services written for ctf-gameserver, Hackerdom, ForcAD or enochecker3 events, without rewriting them for a new platform.
We design linked missions around your scenario, each about two hours with a debrief, then run the exercise or hand it over. Exercises we have run covered ransomware and exfiltration, IAM escalation, and CI/CD supply-chain compromise.
Deploy the services, open the network, let the teams fight, then evaluate with the export. Choose a phase to see what happens in it.
Deploy. Register each service with its checker and pin the images. Teams form and read the services on their own box.
Attack/defence rewards the skills that matter on a real incident: reading unfamiliar code, patching under pressure, and automating what works.
One person watches checks and patches, another writes exploits, another runs the farm. The exercise rewards the coordination a real incident demands.
Up to 256 numbered teams, a public scoreboard, and certificates learners can verify after the event.
Run it on a host nobody else shares, with an export that records every tick for the review afterwards.
A host sized to the roster, fair checking with evidence, and the checkers you already use imported as they are.
From participants and the facilitator of the Athena Cyber Defense Challenge, a cyber range exercise our team ran for Tiller. Logos are organizations we have worked with.
I have been involved in 737 flight simulations to handle emergencies, this was a great simulation to handle our cyber security issues.
As an experienced software engineer who takes security seriously, this exercise gave me first-hand experience of a ransomware incident without the consequences of a real one. I highly recommend it for software teams looking to strengthen their security culture.
Very realistic scenarios, be prepared to actually use skill. The best I've seen across platforms.
Organizations we have worked with


Four things an organization gets from an attack/defence event on Athena that a subscription to someone else's lab library does not.
Every event runs on a dedicated host created after the roster locks and destroyed at the end. Identical hardware for every team, and no other customer on it.
Bring the services your team must defend and the checkers you already have, or hand us a brief and we build the range around it.
Fair-checking findings, every restore and every tick's store states are kept and exported, so the final scoreboard survives the argument afterwards.
Attack/defence is on the Pro plan at a published monthly price, with the host billed by the hour. Have us run the whole event when you would rather not.
The questions security leads, organizers and procurement ask before they run attack/defence on Athena.
Every team defends an identical box running the same vulnerable services. Each tick, a checker plants fresh flags in every team's services and reads earlier ones back. Teams patch their own box, exploit everyone else's, and submit the flags they steal.
A live scoreboard during the game, certificates you can issue to players, and a final export that records every tick's service states, every restore and every fair-checking finding with its evidence.
Yes. A service is any container image, and its checker speaks the service's own protocol. Two public base images run checkers written for ctf-gameserver, Hackerdom checksystem, ForcAD and enochecker3 unchanged.
The event runs on a host dedicated to it, created after the roster locks and destroyed at the end. Boxes have no internet access unless you allow a destination, and the host holds no credential that works outside your event.
An account on the event site, WireGuard and an SSH client. Each player downloads a personal VPN config that routes only the game network and registers their own SSH key for the team's box.
Up to 256 admitted teams, each with 1 to 16 vCPU, up to 64 GiB of memory and up to 512 GiB of disk. Attack/defence is on the Pro and Enterprise plans, and the dedicated host is billed by the hour.
A broken box goes back to its clean snapshot. If the host or checker runner stops reporting, the game pauses itself and nobody is scored down for the outage. A checker of your own that crashes is scored Down, so test it with a diagnostic first; an imported checker that crashes is Cancelled.
Yes. We set up, run and support a complete attack/defence event on Athena, or design a cyber range exercise around your scenario and run it for you.run a complete attack/defence event
Request a custom exercise, book a demo, or create the event yourself on Pro or Enterprise.
Prefer to run it yourself?
See the plans.