Request
Public entry starts in the waitlist. Every account request is reviewed before access is approved.
Reviewed access for a security platform that treats runtime exposure, operator access and event flow as separate concerns.
PWN the room is being built as a controlled CTF surface. Public pages stay simple, challenge labs stay gated, and early access is issued deliberately while the platform hardens.
Access expands in reviewed batches.
Challenge runtimes stay off the public plane.
Internal workflows are not open by default.
Public entry starts in the waitlist. Every account request is reviewed before access is approved.
Approved users complete verification and enter the CTF host with environment-specific credentials.
When a challenge needs a lab, the platform issues a controlled VPN profile instead of exposing the runtime directly.
Events, scoring and writeups stay visible, while the risky parts of runtime access remain gated.
The public layout should explain the product shape quickly: disciplined access, measurable competition and infrastructure that does not pretend every surface is public.
Public pages stay readable and event-oriented. The CTF host carries the authenticated experience, not the marketing surface.
Labs are short-lived, isolated and provisioned behind the runtime control plane. The product is built around controlled exposure, not convenience shortcuts.
The first pilot waves stay intentionally narrow while the infra, security gates and operator workflows harden on real traffic.
The portal stays transparent about active events and public ranking without exposing the runtime plane directly.
Current public competition windows.
A compact look at current public ranking.
Continue on the dedicated CTF host and enter through the authenticated join flow.