Best way to get no-KYC compute for scraping at scale?

Every big cloud provider wants a card + phone verification tied to a real identity now, which isn't great when you're running a few hundred scraper instances that might get flagged and killed.
What's should I use instead? shady VPS, instance rotations, something else entirely?

I'd avoid building a workflow around providers that are easy to replace because they'll usually disappear just as quickly. If you're running a large number of instances, it's worth looking at providers that are transparent about their policies and support automation instead of constantly fighting verification. I'd also design the scraping setup to be resilient so losing an instance doesn't interrupt the whole pipeline. In the long run, a stable infrastructure is usually cheaper than spending time replacing blocked servers.

If you're running hundreds of instances, I'd focus less on avoiding verification and more on making the system fault-tolerant. Instances will get flagged eventually no matter where they come from. Use automation, rotating infrastructure, and good monitoring so losing a server is a minor inconvenience rather than an outage. Stable providers with clear policies usually save more headaches than constantly hunting for disposable VPSs.

restlex said:

Every big cloud provider wants a card + phone verification tied to a real identity now, which isn't great when you're running a few hundred scraper instances that might get flagged and killed.
What's should I use instead? shady VPS, instance rotations, something else entirely?

Click to expand...

You would probably buy vps using middle men as anything could come up and verification will be required

hmmmm, maybe you should probably look at smaller VPS providers instead of the big cloud platforms. A lot of people also spread things across multiple providers instead of relying on just one, so if something gets flagged it doesn't take everything down.

if you need hundreds of instances getting killed, the bigger problem is probably the scraping setup, not KYC… i’d use a legit provider, slow things down, follow site limits and use APIs where possible instead of chasing shady VPS