Google has an organization-wide ban on using AGPL software, and they explain why here:

https://opensource.google/documentation/reference/using/agpl...

I don’t get the blanket ban on AGPL-am I misunderstanding how attach-y it is?

For example, people seem to have the impression that if you host something like an AGPL email validation service that just has an API to request a check for an email and then connects via SMTP, which another service calls, that you “infect” your product that even uses that API.

I get that if you change the service and/or expose it publicly you have to make the changes available, but it seems misunderstood.

It might be: but as a creator of software one wants to make their users happy. We certainly do we at Sentry.

Even personally, years ago I relicensed all my GPL code to BSD/MIT because I wanted people to use my software. I’m not there to tell them that they are wrong about their license restrictions.