Stop maintaining your own Puppeteer setup. There is a simpler way.

Stop maintaining your own Puppeteer setup. There is a simpler way. If you have a Puppeteer instance running in production, you know the maintenance tax. Chromium updates break things on a schedule you do not control. Memory leaks accumulate until you are restarting the process on a cron job. Concurrency requires you to either queue jobs yourself or spin up more instances and manage a pool. And all of this is running on infrastructure you are paying for, for a feature that is almost certainly not your core product. I have seen this pattern dozens of times. Someone needs screenshots for their app. They set up Puppeteer. It works locally. It mostly works in production. Six months later, they are debugging a timeout issue at 2am for a feature that generates social cards. The real cost is not the server. It is the hours. The patchwork alternative is not much better The usual escape hatch is to pay for multiple SaaS tools. A screenshot service here, a PDF generator there, an OG image tool so