Findings
Deterministic architecture findings, reported with the evidence they were derived from.
Local-first Azure architecture analysis
Turn Azure configuration into explainable topology, findings, and routing analysis — while Azure credentials stay local to the operator workstation.
One collected environment in the Workbench: the inventory behind the analysis, the topology drawn from it, and the context of what was collected.
Topology derived from a collected network graph: virtual networks, subnets, peerings, and the controls attached to them.
Derive relationships from Azure evidence so VNets, subnets, route tables, and security controls can be reviewed as one architecture model.
Radivum sits beside Azure's own tools. It reads your network with a read-only sign-in and creates nothing in the client's subscription.
| Tool | Good at | Needs in the client's subscription | Where Radivum fits |
|---|---|---|---|
| Portal topology (Network Watcher) | Drawing what is deployed | Read access | Adds findings, routing and security evidence, and reachability on the same data |
| Network Watcher diagnostics | A live check of one flow | A running VM to test from | Answers the same question from configuration for any subnet pair, with no VM. It does not run live tests. |
| Network Verifier | Reachability with path and blockers, including Azure Firewall at layer 4 | A Network Manager, running VMs, a supported region | Read access only, with a whole-estate matrix. It does not evaluate firewall rules. |
| Defender for Cloud, Advisor | Continuous per-resource recommendations | Enabled in the subscription (attack paths need a paid plan) | Keep them on. Radivum adds how networks, routes and peerings fit together, plus a report to hand over. |
| Resource Graph | Queries | Read access | Relationships already derived, with findings and evidence |
Radivum does not capture packets or run live connectivity tests. Use Network Watcher for live diagnostics; use Radivum to see where to look.
Deterministic architecture findings, reported with the evidence they were derived from.
Route tables and the subnets that rely on them, so routing paths can be reviewed.
Network security group coverage, segmentation, and public exposure in one view.
Explain how a connectivity claim was reached, from evidence to conclusion.
Findings, routing detail, and trace depend on the evidence an analysis source provides. The workbench states what a source supports instead of showing results it cannot prove.
Azure access happens on the operator machine. The Workbench reads normalized evidence and never asks for Azure credentials.
Azure subscription and network resources in scope.
radivum-oss / Pro agent runs on the operator workstation.
NetworkSnapshot and NetworkGraph artifacts.
Interactive topology and architecture analysis in the browser.
Azure credentials remain on the workstation.
Your Azure credentials never enter Radivum.
Azure access uses operator identity on the workstation and collection is read-only. A graph you select is analysed in the browser session, and a connected analysis is stored durably in the workspace of the signed-in account.
Azure identity, local collector, and Workbench run locally.
Subscription resources are read through read-only management access.
Credentials stay on the workstation.
Collect and analyse a local network graph in the browser, including the sanitized demo environment.
Install: dotnet tool install --global radivum-oss
Adds connected local agent collection and richer evidence. The agent collects on the operator workstation with their own Azure sign-in.
Connected agent collection is part of the Pro edition.
Radivum is currently available for free evaluation during Public Preview. Explore Azure network topology, routing, security, and configuration-based reachability analysis. Features may evolve based on user feedback.
No payment obligation arises from preview use. Any future paid offer will require a separate agreement. See the Terms of use and Privacy notice before creating an account.