Milestone 1 / 7
Register as Captain
Captains apply solo. Commitment is required before squad formation opens.

Seven milestones. One championship. Every step is earned.
Qualification sequence
Milestone 1 / 7
Captains apply solo. Commitment is required before squad formation opens.
Milestone 2 / 7
5–7 minute scenario. Incident judgment + signal vs. noise + basic triage. Only qualified captains advance.
Milestone 3 / 7
Recruit your Ops Lead and Signal Lead. Three roles. One weak link ends the run.
Milestone 4 / 7
30 min · Single-service degradation · Alert triage · Basic RCA · Safe mitigation.
Milestone 5 / 7
20 min · Cascading failure · Cost vs latency · Blast-radius control. One wrong fix triggers the next failure.
Milestone 6 / 7
15 min · Black-box outage · Logs limited · Traces only. Infer root cause. Decision speed wins.
Milestone 7 / 7 · Finale
30 min · Multi-service collapse · Misleading alerts · Hidden config issues · Live leaderboard · Stakeholder pressure · RCA required. Survive this — and you've earned your throne.
Season one
Season one is the pilot arena. No invented testimonials — these are the outcomes we engineered Warforge around from day one.
Warforge is built for triage under ambiguity — the same muscle you use when dashboards lie and the clock does not.
Three roles, one scoreboard. Commander, Ops, Signal — every handprint on the outage is visible when the round ends.
Season one is the pilot run: tighter field, sharper feedback, and a format we will keep hardening with every cohort after this.
Who should join
Warforge is not a trivia night. It is for people who have stared at a flat line on success rate, debated rollback vs hotfix, and meant it when they said “I am on it.”
CI/CD, infra glue, prod paths
SLOs, error budgets, wake-up muscle
Multi-region, cost vs latency
Paved roads, guardrails
Clusters under stress
Services in the blast radius
Hungry, qualifier-gated