Galileo vs PDQ Deploy & Inventory: Which is best for you?

Very smart, customer-focused engineering teams make deploying and supporting Galileo low risk and cost effective

We would like to be able to send alerts to distribution lists defined and controlled at our site so that the Galileo configuration does not have to change (e.g. the on-call paging), but with the monitoring hosted at AWS, email alerts take so many hops in AWS to our site and back out to MS365 ( hosted elsewhere) and through those mail hosts, that email alerts are rejected by cloud mail servers (over which we have no control) because they have been forwarded too many times ; we cannot leverage our on-site DLs and have to manually update the addresses in the Galileo GUI, which is tedious

I love the fact that Inventory can provide a dynamic list of endpoints that meet certain criteria (OS, software version, etc.) and present it to Deploy for software or script deployment.

To be honest, I am unable to find any drawbacks, except the Inventory not doing as good job with Windows 11 machines.