Why nix-topology might be the quiet repo that defines how infra teams document next year
A sysadmin I know spent two afternoons last quarter redrawing a Visio diagram that was three months out of date the moment he finished it. The servers it described had already been renamed.
Setting
Infrastructure diagrams have always had a synchronization problem. The machines change; the drawings don't. For teams running NixOS — an operating system where your entire system configuration lives as code in a single declarative file — the irony is especially sharp. Every interface, every hostname, every network link is already written down, in the config. Someone just had to connect those dots.
That someone is oddlama, a developer who built nix-topology as a Nix flake (think: a self-contained, reproducible package for the Nix ecosystem) that reads your existing NixOS configurations and generates SVG network and infrastructure diagrams automatically. No separate diagramming tool. No manual drag-and-drop. The config is the source of truth, and the diagram follows.
With 933 stars and a last commit in May 2026, the project is clearly alive and quietly gaining attention — but it hasn't broken into the wider DevOps conversation yet. That gap, I think, is temporary.
The Story
Here is the concrete picture. Say you manage four NixOS machines: a home router, two home servers, and a VPN gateway. Each machine's configuration file already declares its network interfaces, IP addresses, and which services run on which ports. With nix-topology, you add a small module to your Nix flake that imports those configurations, run nix build .#topology, and get two SVG files — a network view showing how the machines connect to each other and the internet, and a main view showing per-host details like interfaces, addresses, and running services.
The demo output at the project's homepage shows a complex multi-host setup rendered cleanly: colored node cards per host, labeled links between them, icons for service types. It looks like something a network engineer would spend a morning drawing by hand — except it was generated in seconds from configs that were already written.
The critical property is that the diagram updates when the config updates. Rename a host in your NixOS flake, rebuild, and the diagram reflects the change instantly. This is not a novelty feature; for teams that do quarterly audits or hand documentation to new engineers, this is weeks of maintenance work disappearing.
The Insight
Here is my prediction, offered with full willingness to be wrong: nix-topology is going to get meaningfully more visible over the next one to two months, for a specific reason. NixOS adoption among serious home-lab operators and small infrastructure teams has been accelerating steadily through 2024 and 2025. As those users mature their setups — more machines, more VLANs, more services — the documentation pain gets acute. nix-topology is precisely the tool that solves that exact pain, and it appears in search results right when someone is frustrated enough to look for it.
There is also a broader signal here that goes beyond NixOS itself: infrastructure-as-code is moving toward configuration-as-documentation. The idea that your deployment config should be the only place you ever write down what your system looks like — and that visualizations, docs, and audits should all derive from that single file — is gaining real traction. Tools like nix-topology are early proof-of-concept for that model. If you are watching where DevOps tooling is heading in the next 12 months, the "diagram as a build artifact" pattern is worth adding to your mental map.
I would not bet money on the timeline, but I would watch the star trajectory on this one. Repos that solve an annoying-but-specific pain point for a growing community tend to have a sudden rather than gradual climb.
If you find yourself tracking these early-signal repos — the ones sitting quietly at under 1,000 stars before something clicks — that's exactly the kind of story we cover regularly at teum.io/stories.
한국어 요약
nix-topology는 NixOS 설정 파일을 그대로 읽어 네트워크·인프라 다이어그램 SVG를 자동 생성해주는 도구입니다. 별도의 다이어그램 툴 없이, 설정이 바뀌면 그림도 자동으로 업데이트됩니다. 현재 스타 933개로 아직 주목도가 낮지만, NixOS 사용자 층이 빠르게 성장하면서 조만간 급부상할 가능성이 높다고 예측합니다. '설정이 곧 문서'라는 인프라-애즈-코드 트렌드의 흐름과도 정확히 맞닿아 있어 주목할 만합니다.
The config is the source of truth, and the diagram follows.