Cloudflare Tunnel Connector Sizing Calculator: How Many Replicas

What these numbers assume

• Connectors scale with the redundancy level you pick and add a further set per 1,000 active users. Cloudflare documents that each cloudflared instance already opens four connections to four servers across at least two data centers, so extra replicas buy you host-level redundancy, not edge-level redundancy.
• Bandwidth uses a flat 5 Mbps per concurrently active user. That is a planning placeholder, not a measurement. If your traffic is video, backups or large file transfer, raise it; if it is thin internal web apps, lower it.
• Posture evaluations is arithmetic on your own inputs: the user count multiplied by the number of checks per hour implied by the frequency you selected. It counts one enrolled device per user, so if your people carry a laptop and a phone, double it. It is useful for reasoning about log volume and client chatter, not for capacity on Cloudflare's side.
• Not modelled: latency. Round-trip time depends on user location, edge proximity, origin distance and application behaviour, and any single figure printed here would be invented. Measure it from where your users actually are.

Hard limits to check against

Cloudflare publishes per-account Zero Trust limits. These are the ones that constrain a growing deployment:

• Access applications per account: 500
• Rules per application: 1,000
• Domains per application: 50
• cloudflared tunnels per account: 1,000
• Routes (CIDR + hostname) per account: 1,000
• Identity providers: 50 · Service tokens: 50

Your 18 ingress routes use 3.6% of the 500-application account limit.

Source: Cloudflare One account limits. Limits change; check the current page before designing around one.