The hidden cost of running your own browsers isn't just the ~$20 pods. It's the balancers, the scaling, and the hours of engineering time that never quite make it reliable.
Norbert from Dune breaks down the real math behind DIY browser infrastructure.
Read the full story here:
Browser infrastructure that scales with you ๐
Run scraping, automation & testing without managing browsers.
browserless.io
Joined February 2018
- New /agent/run endpoint spins up an AI browser agent from one call. Send a task in plain English, get clean JSON back. Multiple API keys per account are available, so every app or teammate gets its own. You can also scrape mobile sites as a real Android device. Full August
- Reliability isn't a nice-to-have when your product runs on data. Norbert Durcansky at @Dune went from ~10% of browser requests failing or retrying to zero after switching to @browserless. That's the difference infrastructure makes.
- Not every site you scrape needs a residential IP. Datacenter proxies are live: 2 units/MB instead of 6, a third of the cost. At high volume, that gap adds up fast. Switch it with one flag for the easy targets, keep residential for the sites that actually fight back. Learn
- Your browser automations can now log in straight from your @1Password vault. No more pasting passwords into scripts or env vars. Connect once, and the credentials go from vault to browser and nowhere else. They never touch your code or your logs. Learn more:

