The common advice is that self-hosting beats a SaaS API once you hit real volume. That is true, but not for the reason usually quoted. Servers were never the expensive part. Anti-bot bypass and maintenance are, and where your targets sit on those two decides which option is cheaper.

SaaS: the cost hides in multipliers

The headline rate is low, near $0.13 per 1,000 requests for plain HTML on the cheap end. But a JavaScript render costs more, and an anti-bot bypass costs a lot more. On one common API a standard page is 1 credit, a Cloudflare or DataDome bypass adds 10, and Google or LinkedIn run 25 to 30 each (per that provider's published rate card). A plan sold as 100,000 pages shrinks fast once your real targets need rendering and bypass.

Self-hosting: two costs the quote leaves out

A VPS is $20 to $50 a month, and a machine for headless browsers is $100 to $200. That is the number people quote. It skips the two that actually move the total:

• Proxies. Protected targets still need residential IP rotation. That cost does not disappear when you self-host, it moves to a separate proxy bill instead of sitting inside the API price.
• Engineering time. Markup changes, anti-bot updates, flagged IPs. Maintenance runs about 4 to 8 hours a month for an easy target and 20 or more for a protected one. At a normal developer rate this is usually the biggest line item, and the one most estimates ignore.

So which is cheaper

It depends on how protected your targets are, not volume alone. Easy sites that accept datacenter IPs are hard to beat on a cheap per-page API. Heavily protected sites carry a large SaaS premium for the bypass, so your own pipeline with your own proxies pays the raw cost without that markup. The 2026 pricing writeups put the rough crossover where a managed bill passes about $5,000 a month, but target difficulty moves that a lot.