I could be wrong but let's see how wrong I really am.
Though I am not lawyer/license expert so that fact may be irrelevant more so using it as desktop app. But perception matters, if Goog/MSFT are not using it, a startup also won't risk using them lest some auditor flags it in next round of funding particularly if alternative is few dollars a month.
>lest some auditor flags it in next round of funding
i am an auditor and a laywer, so what is there to flag? please enlighten me.
Basically, you if you provide this software as a service to your customers, you are required to let them access the source code and modifications.
the source code of "this" software and any modifications you made. so.... whats the problem?
The problem with AGPL is, that the definitions are very open to interpretation. What is a network, how many systems do have to be between to the end user and the software component to still count as "interacting over a network", etc.
So I would also not recommend to use AGPL in your company...
Edit: we've had to ask you this at least once before: https://news.ycombinator.com/item?id=32387908. Can you please stick to the rules when posting here? We have to ban accounts that won't, and I don't want to ban you.
This is pure fud. Nothing else.
AGPL DOES NOT restrict ability to be used internally. Agpl does NOT restrict selling software as it is.
Agpl does not restrict using agpl software with proprietary software.
Only thing that agpl prevent is, IF YOU MODIFY AGPL SOFTWARE, YOU HAVE TO GIVE SOURCE CODE TO USERS. Your modifications. Thats it.
AGPL DOES NOT MANDATE upstreaming modifications. You can do it or you cannot. Your choice. Others can choose to upstream or fork or Downstream your modifications
What you are confusing with is the fud google spreads about agpl. They dont touch it because if they modify code they have to release it but they don't for reasons known to them.
Again, AGPL is NOT viral like SSPL which is like AGPL but on steroids.