I built Irondiff because I was tired of staring at notepad sessions at 2 AM trying to spot a single line of configuration drift that took down a client site. While diff is great for code, it’s a pain for scrolling through massive Cisco IOS or Juniper config dumps, especially for our Tier 1 techs who aren't CLI wizards.
Irondiff is a visual tool to solve that specific headache.
What it does: It takes two config files (yesterday vs today), normalizes them, and highlights exactly what changed. It supports the weird syntax nuances of Cisco, Juniper, pfSense, Fortinet, etc.
Why I turned it into a SaaS:
I originally scripted this for internal use, but we realized we needed better visibility across our team. I added an API and webhooks so we could pipe alerts directly into Slack and Microsoft Teams whenever a config changed. Now, if an engineer makes a change, the whole team sees the diff in chat instantly.
Pricing:
There is a free tier for basic diffs.
The paid plans ($49/mo and $190/mo) are for the API access, team notifications, and longer history retention. I’m bootstrapping this, so the pricing is designed to sustain the infrastructure without VC money.
I’d love to hear your thoughts on the diff visualization or any edge cases with specific hardware vendors we might have missed.
MattRos•1h ago
I built Irondiff because I was tired of staring at notepad sessions at 2 AM trying to spot a single line of configuration drift that took down a client site. While diff is great for code, it’s a pain for scrolling through massive Cisco IOS or Juniper config dumps, especially for our Tier 1 techs who aren't CLI wizards.
Irondiff is a visual tool to solve that specific headache.
What it does: It takes two config files (yesterday vs today), normalizes them, and highlights exactly what changed. It supports the weird syntax nuances of Cisco, Juniper, pfSense, Fortinet, etc.
Why I turned it into a SaaS: I originally scripted this for internal use, but we realized we needed better visibility across our team. I added an API and webhooks so we could pipe alerts directly into Slack and Microsoft Teams whenever a config changed. Now, if an engineer makes a change, the whole team sees the diff in chat instantly.
Pricing: There is a free tier for basic diffs. The paid plans ($49/mo and $190/mo) are for the API access, team notifications, and longer history retention. I’m bootstrapping this, so the pricing is designed to sustain the infrastructure without VC money.
I’d love to hear your thoughts on the diff visualization or any edge cases with specific hardware vendors we might have missed.
Thanks!