DEV.co
Open-Source DevOps · scanopy

scanopy

Scanopy automatically discovers and visualizes your network infrastructure by scanning devices and services, then generates up-to-date diagrams in multiple formats (SVG, Mermaid, Confluence). It replaces manual network documentation with a continuously refreshed model that captures actual infrastructure state, including physical topology, logical subnets, workloads, and application dependencies.

Source: GitHub — github.com/scanopy/scanopy
5.1k
GitHub stars
250
Forks
Rust
Primary language
AGPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryscanopy/scanopy
Ownerscanopy
Primary languageRust
LicenseAGPL-3.0 — OSI-approved
Stars5.1k
Forks250
Open issues47
Latest releasev0.17.3 (2026-07-04)
Last updated2026-07-07
Sourcehttps://github.com/scanopy/scanopy

What scanopy is

Rust-based daemon that performs scheduled network scanning via SNMP, LLDP, ARP, and Docker discovery to build a model of L2/L3 topology, containerized workloads, and 230+ service definitions. Multi-daemon deployment supports distributed scanning across VLANs; output includes SVG/Mermaid exports, live embedded views, and API access to the topology model.

Quickstart

Get the scanopy source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/scanopy/scanopy.gitcd scanopy# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

DevOps & Platform Teams

Automatically map container, VM, and hardware dependencies without per-device agents. Trace service topology for troubleshooting and capacity planning without APM overhead.

Network Operations

Replace draw.io diagrams with self-maintaining L2 and L3 topology derived from SNMP and LLDP. Multi-VLAN and multi-site topologies update on schedule, eliminating diagram staleness.

Managed Service Providers (MSPs)

Generate per-client network documentation with shareable live views. Reduce manual onboarding and documentation overhead across customer accounts.

Implementation considerations

  • Validate SNMP community strings, Docker API access, and network segment reachability from daemon placement before production rollout.
  • Plan daemon placement for multi-VLAN environments; single daemon in one segment may not reach all subnets without additional daemons or routing.
  • Configure scan frequency based on infrastructure change velocity and acceptable documentation lag (default on schedule).
  • Set up user/RBAC roles and Confluence/SVG export pipelines if sharing network docs across teams.
  • Review AGPL-3.0 source disclosure obligations for your deployment context; consider commercial license if copyleft is incompatible.

When to avoid it — and what to weigh

  • Fully Proprietary Closed Source Required — AGPL-3.0 enforces source code disclosure for network services. If your deployment cannot satisfy copyleft requirements, commercial license from vendor is required (separate contract).
  • Air-Gapped or Highly Restricted Networks — Requires outbound scanning capability (SNMP, Docker API, ARP, LLDP). Tight egress filtering or air-gapped segments may require custom daemon placement or architectural adaptation.
  • Real-Time Packet Analysis or Deep Inspection — Scanopy discovers via service probes and inventory queries, not deep packet inspection. If you need flow-level telemetry or packet-level forensics, pair with dedicated tools (NetFlow, Zeek, etc.).
  • Minimal Infrastructure Footprint — Requires a server component (UI, API, orchestration) plus one or more daemon instances. Docker/Kubernetes deployment adds operational overhead if you only have a few small networks.

License & commercial use

AGPL-3.0 (GNU Affero General Public License v3.0). Self-hosted deployment requires source code disclosure for any network service modifications. Commercial license available from vendor (contact [email protected]) for those unable to comply with AGPL copyleft terms.

Self-hosted AGPL-3.0 deployment imposes source-disclosure obligations for network services; commercially sensitive modifications may trigger compliance requirements. Vendor offers separate commercial license for proprietary deployments. Verify your deployment context against AGPL-3.0 terms or contact [email protected]. Scanopy Cloud (vendor-hosted) operates under separate subscription terms.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Daemon requires SNMP read access, Docker API access, or network scanning permissions to discover infrastructure. Verify credential handling (SNMP community strings, Docker socket/API tokens) and network isolation of the server component. AGPL source code available for audit. No claim of security certification provided; typical network discovery tools carry risk of triggering IDS/alerting if misconfigured.

Alternatives to consider

Netbox + netdisco or Nautobot

Open-source IPAM + network discovery; more mature and broader device support, but requires manual IPAM seeding and custom integrations for application topology.

Cisco Meraki Dashboard or Arista CloudVision

Vendor-provided network visibility; operates at scale with cloud backend, but lock-in to ecosystem and may not cover multi-vendor or legacy hardware.

Observability platforms (Datadog, New Relic, Splunk)

Provide service-dependency maps via APM, but focused on application performance and logs rather than infrastructure topology and network wiring.

Software development agency

Build on scanopy with DEV.co software developers

Scanopy scans automatically and produces up-to-date topology diagrams. Reduce documentation debt and catch infrastructure drift. Start with Docker Compose or try the free demo today.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

scanopy FAQ

Does Scanopy require installing agents on every host?
No. Scanopy is agentless for most discovery (SNMP, LLDP, ARP, Docker API). Docker-native containers are queried via Docker daemon API. Network hardware requires SNMP read access.
Can I use Scanopy across multiple offices or cloud regions?
Yes. Deploy multiple daemons in different segments/VLANs; they report to a central server. Supports distributed topology aggregation for multi-site networks.
What happens if I cannot comply with AGPL-3.0?
Commercial license is available from the vendor. Contact [email protected]. Scanopy Cloud (vendor-hosted) operates under separate terms and does not require self-hosted AGPL compliance.
How often does Scanopy scan, and can I control the frequency?
Scans are scheduled; frequency is configurable. Default behavior updates documentation on a schedule. No real-time/on-demand scanning mentioned in README.

Custom software development services

Adopting scanopy is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source devops software in production.

Keep Your Network Documentation Current

Scanopy scans automatically and produces up-to-date topology diagrams. Reduce documentation debt and catch infrastructure drift. Start with Docker Compose or try the free demo today.