Upstream says each request launches a new browser, so peak RAM rises rapidly with concurrency.
Prowlarr/Jackett users with many Cloudflare-protected indexers.Requisiti hardware di FlareSolverr: RAM, CPU e concorrenza di Chromium
Scopri i requisiti di RAM, CPU, Chromium, sessioni e concorrenza di FlareSolverr, quindi scegli l’hardware ZimaOS più adatto.
FlareSolverr requirements at a glance
FlareSolverr does not publish a numerical CPU or RAM minimum. At idle it uses few resources, but each incoming request can launch a new Chrome browser. Upstream explicitly warns that browsers consume a lot of memory and that low-RAM hosts should avoid many requests at once. Concurrency and persistent sessions—not the proxy API itself—define the real hardware requirement.
- CPU
- No numerical official minimum. Cloudflare challenge solving, JavaScript execution and multiple simultaneous Chrome instances create the main CPU demand.
- RAM
- No numerical official minimum. Upstream explicitly warns that every request can launch a new browser and that browsers consume substantial memory.
- Concurrency
- Avoid many simultaneous requests on low-RAM hosts. Each request can create a separate browser unless a persistent session is reused.
- Sessions
- Persistent sessions keep browser instances alive and can speed repeat requests, but unused sessions should be destroyed because too many can slow the host.
- Architectures
- Current Docker images support linux/386, linux/amd64, linux/arm/v7 and linux/arm64.
- Best Zima starting point
- ZimaBoard 2 832 is a strong normal FlareSolverr host for low-to-moderate request concurrency. ZimaBoard 2 1664 is the safer choice when multiple indexers or concurrent browser sessions are expected.
From official requirements to the right setup
FlareSolverr sizing starts with how many Chromium instances can exist at the same time.
-
Official requirements
Count applications and indexers that can call FlareSolverr concurrently. Every independent request can launch a Chrome instance.
-
Confirm your needs
Use persistent sessions only where they reduce repeated challenge solving, and close them promptly so browser processes do not accumulate.
-
Leave room to grow
Reduce unnecessary browser media with DISABLE_MEDIA when image/CSS/media loading is not needed, lowering bandwidth and some browser work.
-
Run it on ZimaOS
Install FlareSolverr from ZimaOS, generate representative simultaneous requests, then monitor container RAM, Chrome process count, CPU and challenge latency before increasing concurrency.
Check every playback client
- Number of calling apps/indexers
- Simultaneous requests
- Permanent sessions
- Challenge complexity/timeouts
- DISABLE_MEDIA setting
- Container memory limits
- Architecture/Chromium compatibility
- Internet exposure prohibited
Official minimum requirements
FlareSolverr upstream documents browser behavior and architectures but does not publish a fixed host CPU/RAM minimum.
The correct sizing unit is browser concurrency. A host that easily handles one challenge can run out of RAM when several Chrome instances overlap.
| Requirement | Official minimum | What this supports |
|---|---|---|
| CPU | No numerical minimum published | Chrome/Selenium challenge solving determines active CPU demand. |
| RAM | No numerical minimum published | Upstream explicitly warns browsers consume a lot of memory. |
| Default port | 8191 | Current Docker/API listening port. |
| Docker architectures | 386 / amd64 / armv7 / arm64 | Current supported container architectures. |
| Source runtime | Python 3.11 + Chrome/Chromium | Relevant only when installing from source; Docker bundles the browser. |
| GPU | Not required | FlareSolverr uses headless browser CPU/RAM; no dedicated-GPU requirement is documented. |
When to upgrade your hardware
Upgrade FlareSolverr when simultaneous browsers or long-lived sessions create measurable memory/CPU pressure.
Several indexers trigger challenges at the same time
Persistent sessions accumulate
FlareSolverr shares a small host with the full *Arr stack
Sessions keep browsers alive for cookie reuse. Upstream warns that too many active sessions may slow the computer and should be destroyed when finished.
Users reusing sessions for repeated protected sites.Prowlarr, Sonarr, Radarr, download clients and browsers can overlap, making whole-host memory more important than FlareSolverr's idle footprint.
All-in-one automation servers.Plan hardware growth with confidence
Scale FlareSolverr primarily by controlling browser lifecycle and concurrency.
Reuse sessions when it reduces repeated challenge solving
Persistent sessions can avoid launching/solving from scratch for every request, but they must be closed when no longer needed.
Trade launch overhead for a controlled amount of persistent browser memory.Disable unnecessary media loading
Current FlareSolverr exposes DISABLE_MEDIA to skip images, CSS and other browser media and save network bandwidth.
Useful on bandwidth-constrained or high-request deployments.Limit caller concurrency
Because browser count drives memory, throttling simultaneous requests is often more effective than simply increasing a container memory limit.
Use measured peak RAM to set practical concurrency.Give browser-heavy stacks more system RAM
When multiple indexers and companion apps genuinely need concurrent browser solves, 16 GB whole-host memory gives more safety margin.
ZimaBoard 2 1664 is a sensible step before a larger NAS platform.Can it run on ZimaOS?
FlareSolverr is currently available in the ZimaOS App Store, with ZimaOS showing upstream v3.4.6 history.
Install FlareSolverr from ZimaOS
Use the packaged Cloudflare/DDoS-GUARD challenge-solving proxy for compatible self-hosted apps.
Open FlareSolverr in the ZimaOS App StoreUse Docker as upstream recommends
The project recommends Docker because the required external Chrome browser is already bundled in the image.
Read FlareSolverr Docker installationDo not expose FlareSolverr directly to the Internet
Upstream explicitly warns that the service can be abused if publicly exposed.
Read FlareSolverr security warningChoose Zima hardware for FlareSolverr
FlareSolverr is browser-heavy only when active. Choose Zima hardware from peak Chromium concurrency and the companion automation stack.
Will FlareSolverr handle occasional challenges or many concurrent browser solves?
Occasional/low-concurrency indexer challenges
ZimaBoard 2 832 provides ample CPU and 8 GB RAM for a normal household automation stack.
- Normal FlareSolverr hostZimaBoard 2 832
Multiple indexers/sessions plus a larger *Arr stack
Use 16 GB whole-host memory for more Chromium concurrency and companion apps.
- Higher-concurrency automation serverZimaBoard 2 1664
- Integrated storage/automation serverZimaCube 2 Pro
No requests-per-second or browser-count guarantee is implied. Challenge complexity, Chrome version, site behavior, sessions, timeouts and co-hosted apps all affect resource use.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Occasional FlareSolverr challenges in a normal *Arr stack. | Low-to-moderate Chrome concurrency and companion automation apps. |
|
Several simultaneous Chrome instances can still create short memory peaks. | Get Now |
| ZimaBoard 2 1664 | Multiple FlareSolverr callers and persistent sessions. | Higher browser concurrency plus Prowlarr/Sonarr/Radarr/download services. |
|
More RAM should not replace session cleanup/concurrency controls. | Get Now |
| ZimaCube 2 Pro | A larger all-in-one media automation and storage server. | FlareSolverr, *Arr stack, download clients, media storage and more simultaneous services. |
|
Choose Pro for the wider media/storage workload, not because FlareSolverr needs 10GbE. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
FAQ topics follow query fan-out around RAM, Chrome processes, concurrent requests, sessions, ARM support and *Arr integration.
How much RAM does FlareSolverr need?
FlareSolverr does not publish a RAM minimum. Upstream explicitly says browsers consume a lot of memory and low-RAM machines should avoid many requests at once.
Why does FlareSolverr use so much memory?
Each request can launch a new Chrome browser. Several overlapping requests or persistent sessions can therefore create multiple browser processes.
Does FlareSolverr keep Chrome open all the time?
Normal requests launch a browser for the solve. Persistent sessions intentionally keep browser state alive until the session is destroyed.
How can I reduce FlareSolverr resource use?
Limit concurrent callers, destroy unused sessions and consider DISABLE_MEDIA when images/CSS/media are unnecessary.
Can FlareSolverr run on ARM64?
Yes. Current Docker images support arm64 as well as amd64, arm/v7 and 386.
Does FlareSolverr need a GPU?
No dedicated GPU requirement is documented. Its resource pressure comes mainly from headless Chrome CPU/RAM.
Can ZimaBoard 2 832 run FlareSolverr?
Yes for normal low-to-moderate concurrency. Its 8 GB RAM gives much more room than small SBC/router-class hosts, but many simultaneous Chrome instances should still be controlled.
Should I expose FlareSolverr through a public reverse proxy?
No. Upstream explicitly warns not to expose FlareSolverr to the Internet because it can be abused.
What sources and further reading informed this FlareSolverr hardware guide?
The current FlareSolverr README defines the browser-per-request model, memory warning, session lifecycle, architectures, Docker recommendation and security warning. ZimaOS confirms the current app and v3.4.6 history. Upstream community reports were used for memory-leak and ARM/Chromium query fan-out.
