How Pytheus works
Pytheus moves from capability data to scores, benchmarks, and ranked decisions through a deterministic engine you can trace.
Last updated September 22, 2026
Pytheus works in a straight line: you describe your program, the platform scores it, and you get benchmarks, recommendations, and a roadmap you can act on.
The flow
You assess your capabilities using the CAMP model, scoring current and target maturity and setting criticality.
Pytheus Intelligence, the platform's scoring engine, derives your scores from those inputs.
It compares you against an anonymized peer cohort for your sector and size through the Pytheus Index.
It generates ranked recommendations, which you evaluate on the Decisions surface and execute on the Roadmap.
The engine behind it
Pytheus Intelligence is the engine that produces scores, benchmarks, recommendations, and roadmap projections. It is deterministic and explainable. The same inputs always produce the same outputs, and every result traces back to the inputs that created it. There is no hidden judgment in the numbers.
That matters because security decisions get challenged. When a CFO asks why a capability ranks where it does, you can show the maturity scores, the criticality, and the rule that produced the result.
What drives scoring
Capabilities drive scoring. Recommendations come from CAMP priority and deterministic rules, not from preference. Contracts let you track spend and renewals and enrich your view of tool coverage, but they do not move your scores on their own. Evidence tells you how much of your posture you can actually prove, without changing the score itself.
To learn the scoring model in detail, see What CAMP is and Understanding maturity levels. When you are ready, go to Completing your first baseline.