I built a native Mac app for NetBox and Zabbix: site map, topology, racks and SSH in one window (open source, v1)
Kia ora all. I'm Leon from Omega Networks in Wellington, NZ. Upfront: our team built this, and the source is AGPL.
The problem we kept hitting: the network diagram is stale the week after someone draws it, and in an outage you're bouncing between NetBox, Zabbix and a terminal trying to work out what's actually down.
Pulse reads your NetBox and draws it for you: sites on a map, a site graph built from your devices and cables, and rack elevations with patch panels. Point it at Zabbix too and devices get coloured by live problems. You can open SSH or a device's web UI straight from the node.
How it plays with your setup:
- Everything stays on your Mac. Nothing is sent to us.
- NetBox v1 or v2 (
nbt_) tokens, HTTPS only. Read-only works for sync; writes (cables, interface descriptions) need write permission. - Zabbix matching uses a
zabbix_idcustom field on the device. API token on 7.2 and later, legacy login on 6.0 to 7.0. - Needs macOS 26 or later.
Source and setup guide: github.com/Omega-Networks/Pulse
What in your NetBox data would break this? And what would get you opening it mid-incident instead of your existing tools?