Curious more than anything. If your intent is to use the tool as opposed to importing the tool as a feature or product, is the AGPL a problem?

Also, "everyone nervous" is an interesting choice of words - I'm pretty sure most people wouldn't really care one way or the other. What is it about AGPL that causes stress among the masses?

> Also, "everyone nervous" is an interesting choice of words - I'm pretty sure most people wouldn't really care one way or the other. What is it about AGPL that causes stress among the masses?

Things like Google's AGPL internal policy[1] existing as a public piece of corporate-friendly IP propaganda have snowballed into a lot of FUD about the license.

People like to parrot perceived and secondhand opinions about the AGPL, and "some companies don't like the AGPL" transformed into "the AGPL makes everyone nervous."

[1] https://opensource.google/documentation/reference/using/agpl...

Fair point.

Clarifications: no, using the tool directly is not a problem for us.

"Everyone" - appreciate your question and not guessing :-) I meant everyone at my company. That phrasing maybe speaks to my mindset :-D Basically I really mean legal and those in charge who might listen to legal over tech.

You’re not building against their code, you’re just using the end product, why would AGPL matter here at all?

They have a commercial license, but just using an AGPL product doesn't mean you must AGPL your project.