Cloudflare recommends two dedicated cloudflared hosts per location. Moving from one home connector to a redundant topology is a host-count/availability upgrade, not simply a RAM upgrade.
Small offices and production services that cannot depend on one host.Hardwareanforderungen für Cloudflared: CPU, RAM, Ports und Tunnelauslastung
Erfahre mehr über die Anforderungen von Cloudflare Tunnel und cloudflared an CPU, RAM, Ports und Redundanz und wähle anschließend die passende ZimaOS-Hardware für Tunnel im Heim- und Produktionseinsatz.
Cloudflared requirements at a glance
Cloudflare now publishes a formal baseline recommendation for Cloudflare Tunnel hosts: for most production use cases, run two dedicated cloudflared replicas per network location, give each host at least 4 CPU cores and 4 GB RAM, and allocate 50,000 ports to the process. Cloudflare also states that cloudflared is lightweight enough to run on a Raspberry Pi, so the 4-core/4GB figure is a production availability baseline—not proof that a small home tunnel cannot run on less.
- Production CPU baseline
- Cloudflare recommends at least 4 CPU cores per cloudflared host for most production use cases.
- Production RAM baseline
- Cloudflare recommends at least 4 GB RAM per cloudflared host for most production use cases.
- Availability
- Cloudflare recommends two dedicated cloudflared hosts/replicas per network location for server-side redundancy and traffic balancing.
- Ports
- Allocate 50,000 ports to the cloudflared process per production host. Cloudflare says tunnel throughput is primarily limited by system port availability rather than hardware.
- Home/low-scale reality
- Cloudflare explicitly says cloudflared is lightweight enough to run on a Raspberry Pi or data-center server. A single low-traffic home tunnel can therefore be much lighter than the production HA baseline.
- Best Zima starting point
- ZimaBoard 2 832 has 4 cores and 8 GB RAM, so one unit clears Cloudflare's per-host production CPU/RAM baseline. A true recommended redundant production topology still requires a second independent replica/host.
From official requirements to the right setup
Cloudflared sizing starts with whether the deployment is a home tunnel or a production high-availability connector.
-
Official requirements
Classify the deployment. For a personal home tunnel, cloudflared can be lightweight; for production, Cloudflare's current baseline is two dedicated hosts per location with 4 cores and 4 GB RAM each.
-
Confirm your needs
Estimate concurrent connections and port consumption. Cloudflare says throughput is mainly constrained by the number of ports configured in system software and recommends allocating 50,000 ports per production cloudflared host.
-
Leave room to grow
Account for origin traffic and redundancy. A cloudflared connector proxies traffic between Cloudflare and local origins; multiple replicas improve availability but also mean separate host/process resources.
-
Run it on ZimaOS
Install Cloudflared from ZimaOS, run representative tunnels, monitor CPU, memory, connections and origin traffic, then add a second independent replica if availability requirements justify Cloudflare's production topology.
Check every playback client
- Home tunnel versus production network connector
- One replica versus two-host high availability
- Concurrent connections and port allocation
- Aggregate tunneled traffic
- Number and type of local origins
- HTTP versus SSH/RDP/private-network use
- Container/service restart behavior
- Other ZimaOS apps sharing the host
Official minimum requirements
Cloudflare's April 2026 system-requirements update provides a current production baseline. It should be described as a baseline recommendation for most use cases, not as the minimum resources required merely to start the cloudflared binary.
For a home server, one ZimaBoard 2 832 already exceeds the per-host 4-core/4GB recommendation. For production availability, hardware sizing also includes a second independent replica/host and adequate OS port capacity.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Production host CPU | Minimum 4 CPU cores in Cloudflare's baseline recommendation | Applies to Cloudflare's recommended production host sizing. |
| Production host RAM | Minimum 4 GB RAM in Cloudflare's baseline recommendation | Applies per recommended cloudflared host. |
| Recommended replicas | Two dedicated hosts per network location | Provides server-side redundancy and traffic balancing. |
| Port allocation | 50,000 ports per cloudflared process | Cloudflare says port availability is usually the main tunnel-throughput scaling factor. |
| Low-resource capability | Lightweight enough for Raspberry Pi | This official statement shows the production baseline is not a binary startup floor. |
| GPU | Not required | Cloudflared is a network tunnel daemon; dedicated graphics hardware has no sizing role. |
When to upgrade your hardware
Cloudflared upgrades are justified by connection scale, availability and the larger service stack.
You need production-grade redundancy
Port or connection pressure becomes the bottleneck
Cloudflared shares a busy all-in-one server
Cloudflare says tunnel throughput is primarily limited by system port availability and recommends 50,000 ports per host. Connection scale can therefore become the next limit even when CPU/RAM remain comfortable.
High-concurrency tunnel deployments.Cloudflared itself may remain lightweight, but origins, reverse proxies, authentication, storage and application containers compete for the same host resources.
ZimaOS servers exposing many local services through one connector.Plan hardware growth with confidence
Scale Cloudflare Tunnel by separating availability, ports and origin capacity.
Add a second replica before over-sizing one host
Cloudflare's recommended topology uses two hosts to remove a single connector host as the availability point of failure.
Use independent hosts/replicas when service uptime matters.Increase OS port capacity for high connection counts
Cloudflare explicitly identifies port availability as the primary tunnel-throughput constraint and recommends 50,000 ports per production process.
Tune the OS/network stack before assuming a faster CPU is the answer.Keep tunnel and origin bottlenecks separate
A slow local web app, disk, database or WAN uplink can limit user experience even when cloudflared has spare CPU.
Size origins and network links independently from the tunnel daemon.Use more Zima hardware for the surrounding platform
A ZimaCube can make sense when the same machine also hosts multi-drive storage, databases, media and many published services.
Upgrade the whole server for the origins and storage workload, not for cloudflared alone.Can it run on ZimaOS?
Cloudflared is currently available in the ZimaOS App Store and provides outbound-only Cloudflare Tunnel connectivity.
Install Cloudflared from the ZimaOS App Store
The ZimaOS listing describes Cloudflare Tunnel as a way to expose web services without opening inbound firewall ports.
Open Cloudflared in the ZimaOS App StoreUse the current Cloudflare system-requirements baseline
For production use, plan 4 cores, 4 GB RAM and two replicas/hosts per location, plus adequate port allocation.
Read Cloudflare Tunnel system requirementsTreat one ZimaOS connector as one replica
One Cloudflared container on one physical host does not create host-level redundancy. A second replica should live on another suitable host when that failure boundary matters.
Read Cloudflare Tunnel availability guidanceChoose Zima hardware for Cloudflared
One ZimaBoard 2 832 clears Cloudflare's per-host production CPU/RAM baseline, but production high availability is a topology decision requiring a second independent host.
Is this a personal home tunnel or a production/high-availability connector?
Personal or low-traffic home tunnel
A single ZimaBoard 2 832 has ample resources for cloudflared and lightweight companion services.
- Home Cloudflare Tunnel hostZimaBoard 2 832
- More network/security apps on the same hostZimaBoard 2 1664
Large all-in-one server or heavier local origins
Move to ZimaCube for the origins, storage and broader application stack; use a second independent host if Cloudflare's HA topology is required.
- Multi-drive origin serverZimaCube 2 Standard
- High local throughput and 10GbE origin stackZimaCube 2 Pro
The 4-core/4GB values are Cloudflare's current baseline recommendations for most production use cases, not a claim that cloudflared cannot run on smaller hardware. Cloudflare itself says Raspberry Pi-class systems are viable.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A home Cloudflare Tunnel host or one production replica. | Cloudflared plus a small set of local origin services. |
|
One box is still a single host failure domain. Production redundancy requires another independent cloudflared host. | Get Now |
| ZimaBoard 2 1664 | Cloudflared plus more network/security and application containers. | More origins and a larger co-hosted ZimaOS stack. |
|
Extra RAM benefits the other services; cloudflared's per-host production recommendation is already met by the 832. | Get Now |
| ZimaCube 2 Standard | A multi-drive application/origin server also running cloudflared. | Cloudflare Tunnel in front of storage, media and self-hosted apps. |
|
Choose it for the origin workload and storage, not because cloudflared needs a Core i3. | Get Now |
| ZimaCube 2 Pro | A larger origin platform with 10GbE local workflows. | Many local services, storage traffic and cloudflared on the same server. |
|
10GbE improves local/origin capacity only when the rest of the path can use it; it does not replace a second HA replica. | 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
These answers distinguish Cloudflare's production baseline from lightweight home deployments.
How much RAM does cloudflared need?
Cloudflare's current production baseline recommends at least 4 GB RAM per cloudflared host. The same official page says cloudflared is lightweight enough to run on a Raspberry Pi, so 4 GB is a production baseline rather than a binary startup minimum.
How many CPU cores does Cloudflare Tunnel need?
Cloudflare's current baseline recommends at least 4 CPU cores per production host.
Why does Cloudflare recommend two cloudflared hosts?
Two hosts provide server-side redundancy and traffic balancing so one physical host failure does not take the connector location offline.
Can ZimaBoard 2 832 run cloudflared?
Yes. Its 4-core Intel N150 and 8 GB RAM exceed Cloudflare's per-host production CPU/RAM baseline.
Does cloudflared need a GPU?
No. A dedicated GPU has no role in Cloudflare Tunnel sizing.
What limits Cloudflare Tunnel throughput?
Cloudflare says throughput is primarily limited by the number of ports configured in system software rather than hardware and recommends allocating 50,000 ports per production process.
Does one ZimaBoard 2 satisfy Cloudflare's high-availability recommendation?
No. It satisfies the per-host CPU/RAM baseline, but Cloudflare recommends two dedicated hosts per location for host-level redundancy.
When should I choose ZimaCube 2 for cloudflared?
Choose it when the same server also hosts larger storage, databases, media or many origin services. Cloudflared alone rarely needs ZimaCube-class hardware.
What sources and further reading informed this Cloudflared hardware guide?
Cloudflare's current System Requirements page is the authority for the 4-core/4GB per-host production baseline, two-host redundancy and 50,000-port recommendation. Cloudflare Tunnel documentation explains the lightweight outbound-only daemon architecture, while Cloudflare's reference architecture notes that cloudflared usually consumes a small amount of CPU and RAM. The official Docker image and ZimaOS App Store confirm current container deployment availability.
