3 ms·

So does that mean that AGPL code isn't suitable if you need to interface it to, for example, an Oracle DB as you don't have the source or rights to release Orac

So does that mean that AGPL code isn't suitable if you need to interface it to, for example, an Oracle DB as you don't have the source or rights to release Oracle (as an example)? If that's the case, then I could see why it would be on the no-list. Google has a bunch of internal secret sauce that may need to be called on by an external-facing app.

bryanlarsen 9y ago
Not at all. You don't have copyright permission to modify Oracle DB, yet you are using it lawfully, therefore via the definition of "modified work" in the AGPL it's not covered by the AGPL.