Oryon Flow vs Hadrian Nova

1. 01

   Work from the exact revision

   Flow prepares an isolated application from the repository; Nova targets a deployed application or staging URL.

2. 02

   Move from findings to source changes

   Flow generates repair candidates and delivers PRs; Nova documents findings and remediation guidance.

3. 03

   Make the expected result reviewable

   Flow relates a proposed correction to its behavior checks and selected technical requirements.

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	Hadrian Nova
Repository investigation	✓Documented Source, packages, infrastructure and runtime connected in one investigation.	—Not documented in this scope Nova starts from an application target; repository investigation is not established on the product page. ↗
Reconstructed test environment	✓Documented Rebuilds the application in ephemeral, isolated environments from the original repository.	—Not documented in this scope A running application or staging environment is supplied; rebuilding it from source is not documented. ↗
Finding verification	✓Documented Independently reviewed proof method: confirmed, refuted or inconclusive. Missing proof remains an open question.	✓Documented Reports exploit proof, reproduction steps and human-reviewed findings. ↗
Fixes backed by tests	✓Documented Isolated candidates; checks security and legitimate behavior before an independent review.	—Not documented in this scope Documents remediation guidance; source-patch generation is not established. ↗
Reviewable pull requests	✓Documented Groups changes by cause and compatibility into reviewable PRs. Your team decides the merge.	—Not documented in this scope Provides actionable reports; publishing corrective PRs is not documented in this scope. ↗
Traceable technical evidence	✓Documented Links proofs and changes to technical requirements; compares current evidence with the projection from verified PRs.	✓Documented Request/response proof, reports and remediation-validation records. ↗
Source + runtime analysis	✓Documented Connects source, dependency, infrastructure and dynamic observations in the same investigation.	—Not documented in this scope Live application exploration is documented; source analysis is not established. ↗
Authenticated role testing	✓Documented Checks legitimate sessions, roles and tenant boundaries; unreachable or expired sessions remain coverage gaps.	✓Documented Tests account boundaries by acting as users and checking access to other customers’ data. ↗
Separate validation	✓Documented The proposing agent does not approve its own conclusion or fix; a separate verification step evaluates retained evidence.	✓Documented Nova findings receive human review in addition to agent execution. ↗
Functional regression checks	✓Documented Compares security proofs, legitimate controls and available functional tests with the original before delivery.	—Not documented in this scope Verifies whether exposed vulnerabilities remain; source-level functional regression tests are not specified. ↗
Dependency fixes	✓Documented Repair candidates can update the dependency graph and adapt application code, subject to validation.	—Not documented in this scope Guides remediation; automated dependency updates are not established for Nova. ↗
Technical requirement mapping	✓Documented Links retained evidence to selected technical requirements and shows current versus proposed coverage; this is not organizational certification.	✓Documented Reports map results to frameworks including SOC 2, ISO 27001 and NIS2. ↗

Product scope