Yeah, definitely a product that you don't realize you need...until you find the issue. As of now it's a pool of headless Chrome instances that you can control

Yeah, definitely a product that you don't realize you need...until you find the issue. As of now it's a pool of headless Chrome instances that you can control remotely and run tasks through. Screenshots, PDFs, scraping... whatever you need. The reason that folks use this is because it's _really scary_ to run Chrome alongside your app's infra, so separating it out (much like a DB) is a good idea. In the near-future we'll offer functions and other REST endpoints for doing common and user-defined tasks. This make it even more contained so your app can keep running happily without babysitting Chrome. Great question!