Mixed challenge formats
Events can combine static tasks, live labs and reviewed community content without forcing every challenge into the same delivery model.
Compete
Structured competition, not random challenge sprawl.
The platform is designed for event pressure that stays readable: clear tracks, visible ranking and runtime access only where it actually matters.
Challenge tracks
The taxonomy is broad enough for serious events, but still explicit about what participants are walking into.
webpwnreversecryptoosintforensicscloudai security
Competition shape
The public surface should explain how events work without leaking runtime complexity into every page.
Visible scoring
Ranking, solves and event movement stay legible to participants. The public layer should explain pressure clearly instead of hiding the competition logic.
Gated runtime access
Only the challenges that need segmented reachability use VPN-backed runtime access. The rest of the competition stays on the ordinary CTF surface.
Participation flow
The path from registration to challenge access should stay short and explicit.
Register and verify your account.
Join the event as solo participant or as part of a team.
Connect to VPN only when a challenge actually requires gated lab access.
Start a lab from the challenge page when the event policy allows it.
Current public signal
Events and leaderboard remain visible even when some runtime surfaces stay gated.
Events
Current public competition windows.
- No public events loaded yet.
Leaderboard
A compact look at current public ranking.
- No public leaderboard data yet.