Just checked the GitHub license page (https://github.com/browserless/chrome/blob/master/LICENSE.md https://github.com/browserless/chrome/blob/master/LICENSE.md)

Just checked the GitHub license page (https://github.com/browserless/chrome/blob/master/LICENSE.md https://github.com/browserless/chrome/blob/master/LICENSE.md). > This work is dual-licensed under GPL-3.0 OR the browserless commercial license. You can choose between one of them if you use this work. So it's clearly GPLv3 (no loophole required), which AFAIK does allow closed source proprietary use within a company so long as the program isn't redistributed externally (perhaps the developer didn't understand that?). It seems that the licensing section in the readme should have it's wording adjusted somewhat. In fact, I think you're even in the clear to run a proprietary cloud service using GPLv3 code which is why the AGPL (among others) exists. Some recent drama (https://techcrunch.com/2019/05/30/lack-of-leadership-in-open-source-results-in-source-available-licenses/ https://techcrunch.com/2019/05/30/lack-of-leadership-in-open...) for reference. (Oddly, the header underneath that states "GPL-3.0-or-later" which is a bit inconsistent.)