Q&A · REV. C
Questions people ask
Four answers per solution, and each one is the same answer support would give you.
Is scraping actually allowed on your servers?
Yes — the acceptable use policy explicitly permits it when it is polite: it respects the target's terms, robots.txt intent and rate limits, and the law of the target's country. The instant-kill list is for credential stuffing, scalping and denial-of-service, not for reading public pages slowly.
How do I avoid getting my IP blocked?
Rate limiting and variety beat raw volume. The routed /64 gives you 18 quintillion addresses for low-risk requests, additional IPv4s cover the sites that distrust IPv6, and a sensible delay between requests keeps both your targets and our abuse inbox quiet.
Can I run the whole stack — browser, queue, database — on one server?
Yes, and the Work plan is sized for exactly that: 16 GB of RAM is the comfort zone for a browser pool with a Postgres or Redis neighbour. If the collection is firehose-scale, the Forge's 32 GB or a second Work plan split by region is the cleaner architecture.
Do you provide proxies or rotating IPs as a service?
No — we sell servers, and each server brings its own IPs. The /64 IPv6 block and cheap additional IPv4s are the honest version of rotation: real addresses from a real AS with a real abuse desk, which is what keeps them working.