What Server Do You Need for Web Scraping and Automation
Count your threads, pick the OS — then run your own scripts on the build during the 5-hour test period, before you pay
Match a configuration
A server for scraping and automation is chosen by three numbers: the count of parallel threads, what operating system your software requires and the volume of data you collect. A practical benchmark: one headless browser takes 0.5–1 GB of RAM, so 8 GB carries 6–10 threads and 16 GB carries 12–20. Python and Node.js scripts are far leaner on memory and run on Linux; ZennoPoster, BAS and CapMonster require Windows. Below are builds for typical scenarios; once you have chosen, order a VPS for automation.
What such a server costs
Standard, Power and Max — monthly or yearly at a discount. Test period of 5 hours before payment.
Standard 1
| 4 vCPU · AMD EPYC |
| 4 GB RAM |
| 50 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 2
| 4 vCPU · AMD EPYC |
| 6 GB RAM |
| 60 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 3
| 6 vCPU · AMD EPYC |
| 8 GB RAM |
| 80 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
A build for a typical scenario
How many threads and how much data each configuration from our price list carries.
| Scenario | Configuration | Plan | Price, €/mo | |
|---|---|---|---|---|
| 1–2 Python scripts started by cron | 4 vCPU · 4 GB · 50 GB | Standard 1 | €5.49 | Order now |
| 6–10 headless browser threads | 6 vCPU · 8 GB · 80 GB | Standard 3 | €8.99 | Order now |
| ZennoPoster or BAS on Windows | 8 vCPU · 8 GB · 100 GB | Standard 4 | €10.99 | Order now |
| 12–20 threads, scraping through proxies | 10 vCPU · 16 GB · 160 GB | Power 1 | €17.99 | Order now |
| Dozens of bots and large exports | 16 vCPU · 24 GB · 240 GB | Power 3 | €27.99 | Order now |
Benchmarks for memory use per thread; the real load depends on the target sites and on your own software. Prices are for monthly billing from our price list — 10 % lower for six months, 18 % lower for a year.
Count memory per thread
Multi-threaded scraping runs out of RAM long before disk: 0.5–1 GB per headless browser plus headroom for the system.
The software picks the OS
Python and Node.js are leaner on Linux; ZennoPoster, BAS and CapMonster run on Windows only.
Proxies and your own IPv4
The server comes with a dedicated IPv4, and any external proxies are configured inside your software — we place no restrictions on that.
How to match a server to your tasks
Three steps — from counting threads to a run on your real scripts.
Count the threads
Multiply the number of concurrent browsers by 0.5–1 GB and add 1–2 GB for the system — that is the RAM you need.
Decide on the operating system
Check which OS your software targets. Windows is only needed for RPA platforms; scripts are fine on Ubuntu or Debian.
Verify it in the test period
The VPS is provisioned in test mode for 5 hours: run your own scripts under real load and pay only after that.
The build is chosen — time to order
Checkout, OS images and plans are gathered on a separate page — VPS for automation. It also describes how the server is provisioned and what the plan includes.
If you already know the software, start from its own page: ZennoPoster, CapMonster or Docker for containerised pipelines.
Go to the VPS order pageFrequently asked questions
Didn't find your answer?
Write to us via the contact page form.
Between 0.5 and 1 GB for every headless browser. On 8 GB (Standard 3, €8.99/mo) you can realistically run 6–10 threads, on 16 GB (Power 1, €17.99) 12–20.
Linux if your scripts are Python or Node.js — it uses less memory. Windows is needed for ZennoPoster, BAS and CapMonster; you pick the image yourself during installation.
With browser-based scraping memory runs out first, so look at RAM. Cores matter more when no browser is involved and the load is HTML parsing and data processing.
Text exports are small: a million JSON rows is a few gigabytes. Plan the disk for logs, screenshots and media: 50 GB NVMe on the entry plan, 240 GB on Power 3.
You need proxies when the target site limits request rates from one address. The server has one dedicated IPv4, and external proxies are configured in your own software without restrictions from us.
With cron or systemd timers on Linux and Task Scheduler on Windows. The server runs around the clock, so your own computer does not have to stay switched on.
Collecting publicly available data is generally permitted, but responsibility for the law, the target site's terms and our own terms of service rests with you. We do not inspect the contents of your scripts.
On the VPS for automation page: plans, OS images and checkout. The server is provisioned in test mode for 5 hours — you pay after checking it.