Foros

I work as a developer for a small US company, and we have several Playwright scripts that collect publicly available information from websites and run routine browser checks. Everything currently runs on our own server, but keeping Chrome updated, dealing with crashed sessions, and managing several browsers at once is becoming a lot of extra work. I've been looking into browser as a service as a possible alternative, although I'm not entirely clear on what actually moves to the provider's infrastructure and what we'd still need to manage ourselves. Has anyone made this switch? How does it work in practice, and what should I consider before moving our scripts?

Some scripts look easy to move until they hit the first file upload or try to save something back to the machine they used to run on. That’s where little dependencies on the local setup start showing up. Take one smaller Playwright script and run it against a remote browser first, preferably one that uploads a file, saves screenshots, or reads something from your server. Check what needs changing for local resources and how much data has to move between your server and the browser session. You’ll get a much clearer idea of the migration work before touching the rest of the scripts.