NetworkLink.EU is a downloadable desktop application for Windows, macOS and Linux. It runs locally on your computer, rather than as a cloud-hosted service.
Keep your infrastructure data private. Your AWS and Azure inventory, snapshots and diagrams are stored locally and are not uploaded to NetworkLink.EU servers. You retain control over what you export and share.
See how your AWS and Azure resources fit together. Investigate network paths, understand what changed, and turn your findings into diagrams.
Explore these screenshots from the desktop app, showing an AWS sample snapshot. Select an image to take a closer look.
Select AWS or Azure in the app’s cloud selector. Each workspace shows its own snapshots, resource types and tools, using the cloud’s own terminology. Monitoring, network tests, diagrams and notes are shared.
Explore AWS accounts, VPCs and subnets, or Azure subscriptions, VNets and subnets. Switch between Structured and Connections maps to view resource groups or relationships. Both clouds offer all four 2D and 3D views.
Search · Filter · Focus · ExpandFind a resource by name or ID and inspect its properties, tags and saved native API responses. Follow recorded relationships in the map and resource details.
Resource details · Raw JSON · Native cloud terminologyCompare two snapshots or follow one resource through its saved history. Review configuration and relationship differences, with collection coverage kept in context.
Before / after · Resource history · Collection coverageEvaluate supported IPv4 and IPv6 flows using each cloud’s saved routing and security configuration. See the decisions and where the evidence runs out. Path coverage differs between AWS and Azure.
Allowed · Blocked · UnknownImport selected snapshot resources and their connections into an editable diagram, or start from a blank grid. Add your own icons, groups, labels, shapes and links.
Custom icon folders · JSON · SVG · PNGExport resource data and diagrams from either cloud. In the AWS workspace, build investigation reports with selected resources, changes, path results, diagrams and notes, and save reusable templates.
Data and diagram exports · AWS HTML/PDF reportsSelect a source, destination and protocol to investigate how the saved configuration treats the traffic. Each workspace applies its own cloud’s routing and security rules.
This is configuration analysis, not a live packet trace. Guest OS firewalls, custom appliances and application behaviour cannot be fully evaluated. An Allowed result describes the saved configuration, not a guarantee of connectivity. Azure appliance, gateway and service-translation paths may remain Unknown.
10.40.10.1010.40.20.20Host firewalls and live application availability remain outside this result.
Go beyond saved configuration with checks from your own computer. Monitor manually entered targets, measure transfers and capture AWS or Azure snapshots on a schedule.
Add IP addresses, hostnames or URLs for ICMP ping, TCP and HTTP/HTTPS checks—including devices outside your cloud environments. Set each target’s interval, timeout and failure threshold, and choose the HTTP status codes you expect.
Review recent results, response times and HTTP headers. Alert and recovery indicators help you spot what happened while you were away. Keep a configurable history and export selected checks or incidents as HTML, with recorded local network details where available.
Per-target settings · Alert history · HTML exportsRun TCP or UDP throughput tests with iperf2 or iperf3. Use the app as a client or server, with one iperf session at a time, and start from built-in test templates. Select your separately installed iperf executable in settings.
Test single or parallel file downloads over HTTP/HTTPS or FTP/FTPS, including S3 presigned URLs. Review throughput, transfer results and errors, then export reports from test history. iperf reports also expose jitter, loss or retransmissions when the tool and test provide them.
iperf client / server · Download tests · Test historySchedule AWS scans with selected connections, regions and services, or Azure scans for a selected subscription across its supported regions and resources. Run at regular intervals or specific times of day, and add a snapshot-name prefix.
Scheduled snapshots appear in the same History and snapshot selectors as manual scans. Pause or run a schedule on demand, and choose whether to skip missed runs or perform one catch-up scan within your configured limits.
Intervals or daily times · Name prefixes · Missed-run controlsMonitoring and scheduled scans run while the app is open and the computer is awake. Monitoring and network tests send traffic to the targets you choose; snapshot-based network path analysis evaluates saved configuration. Live network tests and cloud scans require a valid licence. Transfers may incur network or cloud data charges.
Keep the observation you investigated, the reasoning behind your findings and the diagram that makes them clear.
For AWS, use a read-only IAM role with source credentials or supported direct access keys. For Azure, use a service principal with read-only access to your subscription. Collect on demand or on a schedule, and review successful and incomplete collection results.
Explore the map, inspect raw configuration, compare observations and analyse supported paths. Saved inventory stays available locally for offline investigation.
Turn resources from either cloud into an editable diagram for a ticket, handover or change review. Add notes and export the data you need. The AWS workspace also offers configurable investigation reports.
Choose individual resources, fields, comparison details and diagrams. Snapshot names, dates, scan coverage and raw JSON are optional. Preview the result before exporting HTML or PDF.
Selected resources · Configuration findings · Engineer notes
Purpose-built views help you find the address, rule, resource or change behind an investigation.
Search IPv4 and IPv6 addresses, CIDR ranges or partial IPv4 prefixes. Find recorded addresses and matching AWS VPC, Azure VNet and subnet networks.
Combine resource filters and saved searches. Group by tags, search tag keys and values, and check for missing tags.
Inspect AWS security groups or Azure network security groups, their rules and associated resources. Follow each cloud’s native security configuration.
Review AWS subnet availability and Azure capacity estimates from recorded address assignments. Coverage and calculation details help explain the figures.
Inspect AWS Route 53 and ACM records, or Azure DNS, hostname bindings and recorded TLS settings. Review certificate expiry where it is available in the snapshot.
Follow AWS and Azure resources across snapshots and save favourites. In the AWS workspace, request relevant CloudTrail event history for additional context.
Choose AWS services for each scan. Inventory coverage and network path-analysis coverage differ; incomplete or unsupported evidence is kept visible.
Collect supported resources in an Azure subscription and follow their native associations. Uncollected targets remain explicit references; a relationship on the map does not prove network reachability.
Every plan includes the same app features. One AWS account or one Azure subscription uses one cloud-account slot. Mix both providers within your plan’s total allowance—for example, two AWS accounts and one Azure subscription on the 3-account plan.
€15per year · billed annually
Connect up to 3 cloud accounts.
€5per cloud account
per year
€20per year · billed annually
Connect up to 5 cloud accounts.
€4per cloud account
per year
€30per year · billed annually
Connect up to 10 cloud accounts.
€3per cloud account
per year
€40per year · billed annually
Connect up to 20 cloud accounts.
€2per cloud account
per year
€50per year · billed annually
Connect up to 30 cloud accounts.
≈ €1.67per cloud account
per year
Per-account prices assume the full account allowance is used; the 30-account figure is rounded. Each plan is billed annually at the total shown. Prices exclude VAT. Any applicable taxes are shown at checkout.
A desktop workspace built around recorded AWS and Azure configuration and the engineer investigating it.
Inventory collection reads AWS and Azure management APIs. You control AWS credentials and IAM permissions, or the Azure service principal and its role assignments. NetworkLink.EU does not create, update or delete cloud resources as part of inventory collection or path analysis.
Yes. AWS and Azure snapshots are stored locally and can be explored, compared and used for diagrams offline. New scans need a connection to the relevant cloud. AWS CloudTrail lookups also need an AWS connection. Both workspaces include sample inventory to explore.
Yes. Your allowance is shared across registered AWS accounts and Azure subscriptions. Each counts as one slot. Choose AWS or Azure in the cloud selector to see that provider’s pages and snapshots; switching workspaces does not change your allowance.
No. Map connections represent recorded resource relationships. Network path analysis separately evaluates supported flows using saved configuration and reports Allowed, Blocked or Unknown. It does not send packets or prove that a live application is reachable.
Export full snapshots as JSON or resource tables as CSV. Diagrams can be exported as editable JSON, SVG or PNG. AWS investigation reports export as HTML or PDF with the resources, diagrams, fields and notes you select. Snapshot JSON can also be imported into NetworkLink.EU. Monitoring checks and incidents, iperf results and download-test results have their own HTML exports.
Yes. Add SVG or PNG icons to folders in your local icon library and refresh it in the app. Saved diagrams embed the icons they use, so your existing diagrams retain their appearance when the library changes.
Explore your AWS and Azure environments with NetworkLink.EU.