Oryon Flow vs Horizon3 NodeZero

1. 01

   Start with the application source

   Flow ties the investigation to the exact repository revision and prepares an isolated target.

2. 02

   Reach the change engineers can review

   Flow includes repair candidates and PR delivery; NodeZero documents remediation guidance and connected workflows.

3. 03

   Protect legitimate behavior

   Flow evaluates the repaired application against prior behavior controls, alongside the security proof.

Capabilities, side by side.

The table describes documented features; it does not measure performance or detection quality. Commercial features may depend on product, plan and configuration.

What you need	Oryon Flow	Horizon3 NodeZero
Repository investigation	✓Documented Source, packages, infrastructure and runtime connected in one investigation.	—Not documented in this scope WebApp testing documents live routes and requests; source-repository investigation is not established here. ↗
Reconstructed test environment	✓Documented Rebuilds the application in ephemeral, isolated environments from the original repository.	—Not documented in this scope Assesses deployed environments; automatic application rebuilding from source is not documented. ↗
Finding verification	✓Documented Independently reviewed proof method: confirmed, refuted or inconclusive. Missing proof remains an open question.	✓Documented Findings carry runtime proof, payloads, responses and practical impact. ↗
Fixes backed by tests	✓Documented Isolated candidates; checks security and legitimate behavior before an independent review.	◇Engine integration Guidance and MCP connect to remediation tools; source repair depends on that external workflow. ↗
Reviewable pull requests	✓Documented Groups changes by cause and compatibility into reviewable PRs. Your team decides the merge.	◇Engine integration Documents an integrated Terraform PR and redeploy workflow, rather than native application patch publishing. ↗
Traceable technical evidence	✓Documented Links proofs and changes to technical requirements; compares current evidence with the projection from verified PRs.	✓Documented Exports finding evidence, requests, responses and reports; re-running verifies WebApp fixes. ↗
Source + runtime analysis	✓Documented Connects source, dependency, infrastructure and dynamic observations in the same investigation.	—Not documented in this scope Runtime attack validation is documented; a combined source-analysis stage is not established in WebApp docs. ↗
Authenticated role testing	✓Documented Checks legitimate sessions, roles and tenant boundaries; unreachable or expired sessions remain coverage gaps.	✓Documented Accepts multiple role-labelled accounts; two roles enable cross-account access and IDOR tests. ↗
Separate validation	✓Documented The proposing agent does not approve its own conclusion or fix; a separate verification step evaluates retained evidence.	—Not documented in this scope Provides exploit proof; a separately authorized verification role is not specified by these WebApp docs. ↗
Functional regression checks	✓Documented Compares security proofs, legitimate controls and available functional tests with the original before delivery.	—Not documented in this scope WebApp fix verification reruns the pentest; functional regression tests on a patch are not documented. ↗
Dependency fixes	✓Documented Repair candidates can update the dependency graph and adapt application code, subject to validation.	—Not documented in this scope Patch management is a complementary integration; native dependency-graph updates are not documented. ↗
Technical requirement mapping	✓Documented Links retained evidence to selected technical requirements and shows current versus proposed coverage; this is not organizational certification.	+Optional / plan dependent Documents CMMC/NIST technical-evidence mappings; scope and organizational controls remain customer responsibilities. ↗

Product scope