SolarWinds Network Configuration Manager review

I use it to manage the compliance of our network devices to configuration hardening standards. Our information security program requires that all our network devices, routers/switches/firewalls/etc, have a defined security hardening standard defined and implemented. As a member of the team, I had to come up with an easy way to measure and demonstrate device compliance to defined standards. I tried setting up regex checks against configs stored in ansible but that required all configs to be in ansible, which they weren't, and so I found myself working edge cases and relying on others who had better things to do than help a security guy. I tried a few config managers including the managing engine NCM, which I used for several years at a previous job, but then migrated to the SolarWinds NCM. I like the SolarWinds NCM interface better and since it is part of the Orion suite and our network team was using Orion I was able to add it to their deployment. If I'm being honest I prefer the management engine interface better but found the functionality to be identical between the two. Most valuable thing is having all the device configs available for testing without relying on other teams.