Thanks. There were some good points raised there specific to the secure remote isolated browser use case.
I'm posting because it's clear that this is more than just a security product. It's a UI and backend to use headless chrome like a regular browser, except in the cloud instead of your device.
The concept is this could perform much better than local Chrome - the cloud has much lower latency to CDN's, a much bigger pipe, and a much better CPU than my phone/laptop for all that javascript.
But the reality (for me at least), is I get a far laggier experience than local Chrome. Hopefully a bit more performance tweaking will flip that.
