Offense + defense · one platform

Attack and defend,
reined in by humans.

R·O·D·E·O — Real-Time Observation, Detection, Exploitation & Optimization

RODEO combines offensive and defensive security operations on one platform, powered by a suite of proprietary AI models, with human-in-the-loop governance gating every action.

RODEO's cyborg bronco mascot — a mechanical horse carrying a banner
Red + Blue
Offense & defense, one platform
Proprietary
Purpose-trained AI models
138
Cross-mapped controls
17
Continuous watchers
R
Real-Time

Streaming telemetry, acted on as events happen — not after the fact.

O
Observation

Sensors, EDR and SIEM fused into one event bus.

D
Detection

ML-ranked findings surface what matters, not noise.

E
Exploitation

Generative exploit drafting validates real-world risk.

O
Optimization

Adaptive response and self-patching playbooks.

One platform, both halves

Offense and defense in one loop

Most tools do one side. R-O-D-E-O runs red and blue on the same platform and the same data, so what the offense finds, the defense learns from immediately.

01 · Attack

Find what is exploitable

Offensive tooling scans and validates real-world risk, with proprietary models ranking what matters first.

02 · Detect

Turn findings into detections

A finding on the offensive side becomes a Sigma / Suricata / YARA detection on the defensive side without leaving the platform.

03 · Defend

Respond, human-gated

Alert triage and approval-gated playbooks act on the new detections. A person signs off before high-impact actions run.

04 · Prove

Evidence for every action

Each step is logged and mapped at the control level, so the purple-team loop also produces compliance evidence.

Offense and defense together ship in the full platform. Need defense only? The Blue / SOC edition ships with the offensive tooling absent from the build. Meet the models →

Full-stack capability map

From telemetry to mission outcomes

From telemetry ingestion to mission outcomes — every layer of R-O-D-E-O is purpose-built, modular, and deployable in sovereign environments.

A1 Mission outcomes

No egress
Runs air-gapped

Local model weights and a local CVE cache. Telemetry is forced off in production; network egress is enforced at the socket layer.

Both halves
One data model

A pentest finding becomes a Sigma / Suricata / YARA detection inside the same platform — purple team as a loop, not an engagement.

138 controls
Compliance at control level

Ten cross-mapped frameworks, 602 resolving cross-references, and an SPRS score kept provisional until a human verifies it.

Human-gated
Graduated autonomy

Low severity auto-approves; medium and above require an analyst. Autonomy is a dial that ships turned down.

A2 Capability stack

R-O-D-E-O modulesCore capability layer
DefenseOffenseIncident ResponseDigital ForensicsReverse Eng.ComplianceICS/SCADASee the architecture →
AI / ML engineProprietary models
Severity classifiersExploit generatorCode reasonerIR · ICS · forensics · defense modelsMeet the models →
Integration layerConnectors & APIs
SIEM / SOAREDR / XDRThreat-intel feedsREST API / SDK
Data sourcesTelemetry collection
EndpointsNetworkCloudIdentityEmailInfrastructure

Telemetry flows up · control flows down

A3 Deployment

Air-gapped

On-premises

Full reasoning with the cable unplugged — local model weights, telemetry forced off in production, and egress enforced at the socket layer.

Build-time

Capability-gated editions

The Blue/SOC edition ships with the offensive routers absent from the build — not disabled, never registered.

Safety-pinned

SCADA / OT

The SCADA profile pins critical-severity auto-approval and patch deployment off, with autonomous concurrency capped at three.

Per-deployment

Nine profiles

Defense, purple, IR, headless, SCADA, cloud, offense, forensics, RE — each with its own autonomy and auto-approval defaults.

Why R-O-D-E-O is different

Four things nobody else can say together

Air-gapped operation alone isn't a moat — Palantir, Elastic, and others are there too. The column that's empty for everyone else is control-level compliance, and the row that's full is ours.

Both halves

Offense and defense, one platform

Everyone else is offense-only or defense-only. A finding on the offensive side becomes a Sigma / Suricata / YARA detection on the defensive side without leaving the platform — purple team as a loop, not an engagement you buy.

Control-level

Compliance, not a dashboard

Ten frameworks, 138 cross-mapped controls, 800-53B baselines, CMMC practice lineage, and an SPRS scorer that produces the number a contractor actually files.

Offline AI

Reasons without internet

Local model weights and a local CVE cache. The difference between a product that installs without internet and one that reasons without it.

OT native

Safety-pinned

ICS watchers and safety handlers, and a SCADA profile that pins critical auto-approval and patch deployment off — in a plant, an automated containment can stop a physical process.

A suite of proprietary, purpose-trained models — severity classifiers, a 285M-parameter exploit generator, and code-reasoning, IR, ICS, forensics, and defense models — runs on local weights inside the perimeter. Autonomy ships turned down: low severity auto-approves, medium and above require an analyst, and eight of nine deployment profiles are semi-autonomous or tighter.