Network documentation shouldn't be a chore
Scanopy exists because keeping network diagrams accurate is tedious, thankless work - and nobody actually does it. We built a tool that does it for you.
How it started
If you've spent any time on r/homelab or r/selfhosted, you've seen the posts. Someone shares a beautifully detailed network diagram - color-coded VLANs, labeled switches, the works - and the comments light up. "How did you make this?" "What tool is that?" "I need to do this for my network."
I was one of those commenters. I always wanted a proper network diagram. I just never wanted to actually make one.
The process is always the same: you open draw.io or Visio, spend a few hours dragging boxes around, feel good about yourself for a week, and then never update it again. Your network changes, the diagram doesn't, and six months later it's fiction.
So I took the technical overkill route and built a tool that scans your network and generates the diagram automatically. That became Scanopy.
How we think about this
Documentation should be derived from infrastructure, not maintained alongside it.
Think of it like OpenAPI specs annotated inline in the codebase - the documentation isn't fully automatic, but it's heavily derived from the technical system it describes. That's the only way it stays accurate. Scanopy works the same way: it pulls directly from your actual network to generate documentation, so the diagram reflects reality instead of someone's memory of reality from three months ago.
A documentation tool shouldn't pretend to be an ITAM platform.
Scanopy doesn't do asset lifecycle management, procurement tracking, or compliance workflows. It does network documentation. That's a feature, not a gap. You don't need a $15/device/month platform when what you actually need is an accurate network map - and our pricing model is aligned to this, so you don't pay per device with Scanopy.
IT buyers don't need hype. They need to verify.
We publish our pricing. We name competitors directly. We show real screenshots, not mockups. We make demos and self-hostability as accessible as possible. If Scanopy isn't the right fit, we'd rather you find out before you deploy it - not after.
The person who set up the network shouldn't be a single point of failure.
Every team has someone who "just knows" how the network is set up. When that person goes on vacation - or leaves - everyone else is guessing. Living documentation fixes the bus factor.
Built by 
mayanayza
I'm a developer and homelabber with over 10 years in tech, spanning B2B SaaS, cybersecurity, privacy, and compliance. I built Scanopy because my own network documentation lived entirely in my head - and I knew I'd never maintain a manual diagram.
Scanopy started as a side project to scratch my own itch. It turns out a lot of sysadmins, MSPs, and network engineers had the same itch.
I'm not an enterprise IT veteran. I've never run an MSP or managed a production data center. What I am is someone who got tired of a problem and built a solution - and then discovered it solved that problem for a lot of other people too.