Thirty minutes to scope a run. Nothing runs until you sign.
Tell us what you want attacked. We come back with the assets in scope, a draft of the rules of engagement and a fixed price. If you would rather look before you talk, walk the product first. No signup.
30-minute call · rules of engagement before anything runs · a run takes 2 to 4 weeks · reports at close
What the call covers
In 30 minutes we walk the loop (observe, reason, attack, validate, report) on the demo environment and map it to the environment you have in mind.
The attack graph
How Radius traces every path to what it reaches and orders them by consequence, not by severity score.
The rules of engagement
What you sign, how the engine enforces it before every action, and where an attack stops.
The reports
Three reports at three levels, the safety trail behind them, and what a re-attack looks like once you fix a path.
Book the call
Leave your name and work email. We reply within one business day to find a time.
How scoping works
Three steps from the form to a signed scope.
- 01
Book the call
Choose a time. We ask a few questions beforehand so the 30 minutes go to your environment, not ours.
- 02
Walk the loop together
We run the loop on the demo environment and talk through what a run against your environment would touch, and what it would not.
- 03
Get a scoped proposal
Assets in scope, a draft of the rules of engagement, and a fixed price. Work starts once you have signed it.
What you are agreeing to
- A 30-minute call, then a written scope and a fixed price
- Rules of engagement signed before anything runs, and enforced by the engine
- A run of two to four weeks, with critical findings communicated as they are validated
- Autonomous testing aligned with the OWASP APTS