I was thinking of building a chrome extension using some open source code licensed under AGPL version 3 for one of my projects. I have modified the original source code quite heavily, and am fine with publishing the modified chrome extension code under AGPL. However, I’m worried about the copy left aspect of AGPL. The new modified extension runs on a chrome browser instance in the cloud or on a user’s own chrome browser. It's only interaction with my other code is that it receives/sends commands via web sockets or http, all over a network. So there is obviously a ton of logical separation between the chrome extension code, and the code that runs the rest of my SaaS.
But I’m also extremely worried about the copy left aspect of AGPL version 3. Would I be required to publish all my code for my entire SaaS or just the extension code? Obviously I’m not an expert on AGPL... =(
Also in response to my post on StackOverflow a user asked for more specifics about how the chrome browser in the cloud worked. So I provided the following example:
"It runs on an ec2 windows instance on aws that automatically loads a chrome browser at launch which then registers itself with the SaaS. The extension receives commands via web sockets, does something in the browser, like takes a screenshot, then sends the results, in this case an image back to the SaaS's own internal apis. The browser version used by front end users is used to build command sets that are then scheduled for execution and relayed to a remote instance at the appropriate time.
Also the reason I'm concerned about copy left is that my SaaS platform has a ton of non-browser related functions which honestly is where my actual value proposition is. The execution of macros in a cloud environment is just one small piece of it."