Scanopy is a Rust-based, AGPL-3.0 network documentation tool for platform and DevOps teams, network engineers, IT operations, MSPs, and home labs that scans infrastructure on a schedule and produces network diagrams that update themselves.

What it is

Scanopy replaces manual network diagrams with a continuously maintained model of what is actually running. A single daemon scans on a schedule, and each scan produces four views: L2 (physical), covering every switch, port, and link; L3 (logical), covering subnets and how hosts connect across them; workloads, spanning bare metal to hypervisors to containers; and applications, covering services and their dependencies grouped by application. The project is written in Rust, published under AGPL-3.0, and can be self-hosted or consumed through the hosted Scanopy Cloud subscription.

The concrete problem it solves is staleness and blind spots in existing documentation practice. Diagrams drawn in draw.io go stale the week they are saved, and IaC state misses drift and resources provisioned outside the pipeline. Scanopy reflects the current state of the infrastructure instead, and the resulting model can be exported as SVG, Mermaid, or Confluence, embedded as live maps, or fed into an existing source of truth.

Key capabilities

• Automatic discovery of hosts and services by scanning the network, using one scanner with no per-device agents.
• 230+ service definitions that auto-detect databases, web servers, containers, network infrastructure, and enterprise applications.
• Four views from one scan: L2 (physical), L3 (logical), workloads, and application dependencies.
• Distributed scanning, deploying daemons across segments to map multi-site and multi-VLAN topologies.
• Native Docker and SNMP integration for containerized services and network hardware discovery.
• Scheduled rescans that keep documentation current as infrastructure changes.
• Multi-user support with RBAC, organization management, role-based access, and shareable live views for teammates or external stakeholders.
• Export to SVG, Mermaid, or Confluence, with live maps that can be embedded.

Who uses it and how

• Platform and DevOps teams trace service dependencies without an APM, mapping containers, VMs, and hardware in one model.
• Network engineers build multi-VLAN, multi-site topology diagrams derived from SNMP, LLDP, and ARP, with no manual drawing.
• IT operations keep inventory, topology, and dependency records current across teams and sites.
• MSPs maintain per-client documentation and hand out shareable live views.
• Home labs document infrastructure without opening draw.io.

Getting started

Self-hosting starts with Docker Compose: fetch the compose file from the repository raw URL and run the mayanayza/scanopy-server and mayanayza/scanopy-daemon images. A hosted option, Scanopy Cloud, is available as a subscription for those who prefer zero infrastructure management.

How it compares

The facts name no paid products this project is positioned to replace, but the README contrasts it directly with manually drawn diagrams in draw.io, which go stale shortly after they are saved, and with IaC state, which misses drift and resources provisioned outside the pipeline. Scanopy sits alongside those tools rather than displacing a commercial category, feeding its model into an existing source of truth where one already exists. The hosted Scanopy Cloud subscription contrasts with self-hosting on the axis of operational burden, since it requires no infrastructure management.

When to use it — and when not to

A self-hoster must operate both a server and at least one scanning daemon, and the AGPL-3.0 licence requires source disclosure for network services plus copyleft compliance. Teams that cannot meet those terms need the separately available commercial licence, and anyone who wants no infrastructure management at all should use the hosted Scanopy Cloud subscription instead. The README excerpt also truncates mid-command in its quick-start section, so the full compose configuration should be checked in the repository before deployment.

curl -O https://raw.githubusercontent.com/scanopy/scanopy/refs/heads/main/docker-compose.yml
docker compose up -d