remote-browser VS browserless

Nice! We built something like this 3 years ago while I was still at Intoli. Instead of Puppeteer we used our own Web Extensions API based framework called Remote Browser [1], the core of which was written by my cofounder.

The tour is still up at [2]. The servers that actually run the Remote Browser have since gone down, but interestingly you can still run the tour. That's because if you don't change the code in the REPL window, you get cached results (except step 7/7 which scrapes Hacker News and won't work). To get those results, we built a little tour "recorder" that would be run on every release. If I remember correctly, we allowed some dynamics ES6 imports through a custom Babel compiler for the code that's input, which also allows first level async stuff, which still works :)

[1]: https://github.com/intoli/remote-browser

The core product is managed, cloud hosted browsers. We run thousands at a time using AWS and DigitalOcean, for people to use with Puppeteer and Playwright scripts. Our container is also available to self deploy under an open-source license.

You should search for "Puppeteer as a service", there are some projects on github that you could deploy such as https://github.com/browserless/chrome

So I recently installed ChangeDetectioIO on my server, it requires either selenium/standalone-chrome-debug:3.141.59 or browserless/chrome. I installed it with Selenium in a docker container since I noticed that it was running better than the browserless/chrome service.

I had a look to this one: https://github.com/browserless/chrome ... but it is not suitable for builds, e.g. set to production mode, user permissions and so on.

git clone https://github.com/browserless/chrome /opt/browserless