4 ms·
If the webapps themselves use AGPL software, that's not "internally." If the employees of a SaaS company themselves use AGPL software that isn't linked to the s
by pessimizer 6y ago
If the webapps themselves use AGPL software, that's not "internally." If the employees of a SaaS company themselves use AGPL software that isn't linked to the service that users access, that's internally; e.g. if a webapp uses an AGPL database, the users are accessing that database.
- fxtentacle 6y agoI'd say using an AGPL tool as a service for your webapp is this scenario: "Scenario 1: Using an unmodified AGPL binary" https://medium.com/swlh/understanding-the-agpl-the-most-misunderstood-license-86fd1fe91275 https://medium.com/swlh/understanding-the-agpl-the-most-misu... which seems to be allowed by AGPL without disclosing source code.
- ghaff 6y agoThe details are somewhat unclear but basically yes, that's what a cloud provider/SaaS company would probably assume. So they probably just won't use AGPL code and if they do want to offer a service with the same APIs, they can (at least for now) recreate a compatible service that they write themselves.