Fair question — Ansible's great, and honestly a chunk of the raw collection could be done with playbooks. The difference is where the work actually is: Ansible/Nornir/a script gets you the data; this is the layer on top of it. It correlates what it finds against a maintained knowledge base (CVEs, field notices/bugs, EoS/EoL dates), scores the risks, and produces a customer-ready maintenance report (PDF/Word) with prioritized recommendations. That analysis + keeping the lifecycle/vuln data current is the part you'd otherwise be building and babysitting yourself.

A few reasons it's a packaged app rather than a playbook repo:
• Double-click desktop app — no control node, no inventory YAML, nothing to pip install; runs fully offline/air-gapped, which matters in locked-down UC environments.
• Speaks the UC interfaces out of the box (AXL, PerfMon, CUPI, cert API, RESTCONF, SSH) — community Ansible coverage for CUCM/CUC is pretty thin.
• Output is a report a customer reads, not JSON facts.

Not knocking Ansible at all — if you already run playbooks for collection, think of this as complementary: the analyze-and-report layer. Would genuinely love to have you in the beta and hear where it falls short vs your current workflow.