Nimbus
Deploy a server

JOB 09 · SCRAPING VPS · AS212345

VPS for scraping and data collection

Collecting public data is a legitimate job that has been chased to the edges of the hosting industry. The Work plan with Docker — 6 vCPU, 16 GB, 200 GB NVMe, €10.40 per month — runs headless browsers and collection stacks properly, and the acceptable use policy says plainly that polite scraping is welcome.

Recommended build

Recommended build

IV Work

€10.40/mo

Work with Docker Engine · 12-month term

Image: Docker Engine on Debian 13

Configure this build

Round trip from Frankfurt

Düsseldorf4 ms
Zurich6 ms
Paris6 ms
Amsterdam7 ms

SPEC · 4 SHEETS

What this workload needs

Four properties that matter for this job, and how the recommended plan covers each one.

01

Headless browsers need RAM, and this plan has it

Sixteen gigabytes is the difference between one Chrome instance and a polite fleet of them. The Work plan runs Playwright or Puppeteer containers with room for the queue, the parser and the database to share the host without negotiating.

02

IPv4 addresses in quantity, IPv6 by the truckload

Each server ships one IPv4 and a routed /64 — 18 quintillion addresses that most sites simply do not rate-limit. Need more IPv4? Eight per server at €1.20 each per month, on the same clean AS212345 ranges we keep abuse-handled.

03

Docker, because collection stacks are containers now

The recommended image is Docker on Debian 13: scheduler, browser pool, proxy pass-through and storage each in their own container, redeployable from a compose file instead of a prayer. When a site changes its markup, you change one image, not the server.

04

Rules that fit the job, enforced the same for everyone

The AUP allows scraping that respects robots.txt intent, rate limits and the law of the target's country — and terminates credential stuffing, scalping attacks and anything that harms other users. We are a host, not a conscience, but the line is drawn where the damage starts.

DATA SHEET · CONDENSED

The short version

Recommended
Work + Docker Engine — €10.40/mo. 6 vCPU, 16 GB RAM and 200 GB NVMe hold a browser pool plus its data.
Bandwidth
12 TB monthly with unmetered inbound — collection traffic is mostly downloads, and we do not double-charge you for it.
IP strategy
One IPv4 + a routed /64 per server; up to eight IPv4s per server. More sites than that means more servers — which the flat price makes painless.
Not offered
Residential proxies, captcha-solving farms or 'unlimited' scraping networks. If the job needs those, it needs a different supplier, and we will say so.
Exit choice
Site by target region: Frankfurt for EU targets, New York/LA for US, Seoul/Tokyo/Singapore for Asia — 2-6 ms to the sites you are reading.

FLEET · FIT CHECK

Plans that fit

The recommended plan is marked. Every plan runs every solution — these are just the sizes we would start with.

PART EVPS-MICRO · REV. D

II Micro

€3.10/mo

billed €€37.20 once· save 21% vs 6-month

vCPU
2 × EPYC
Memory
4 GB DDR5
Storage
50 GB Gen4 NVMe
Traffic
4 TB
Port
1 Gbit/s

Typically used forDiscord or Telegram bot · Mail server · Home lab jump host · Small website

Configure

PART EVPS-WORK · REV. D

IV Work

€10.40/mo

billed €€124.80 once· save 19% vs 6-month

vCPU
6 × EPYC
Memory
16 GB DDR5
Storage
200 GB Gen4 NVMe
Traffic
12 TB
Port
2.5 Gbit/s

Typically used forProduction web app · Postgres primary · CI runner · Scraping

Configure

PART EVPS-FORGE · REV. D

V Forge

€18.90/mo

billed €€226.80 once· save 21% vs 6-month

vCPU
8 × EPYC
Memory
32 GB DDR5
Storage
400 GB Gen4 NVMe
Traffic
20 TB
Port
10 Gbit/s

Typically used forHeavy build machines · Data pipelines · Multiple tenants · Media processing

Configure
Recommended: Work in FrankfurtSee all seven plans

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.