Tunnels for Platforms lets you run more than 1,000 Cloudflare Tunnels in a single Cloudflare account. Every account includes 1,000 tunnels at no cost. With Tunnels for Platforms, you add tunnel capacity beyond that as your deployment grows, without splitting your fleet across multiple accounts.
Tunnels for Platforms uses the same cloudflared daemon, API, and dashboard as every other tunnel. No changes to your tunnels or cloudflared deployments are required.
Tunnels for Platforms is designed for customers who need to create one tunnel per device, end customer, or environment:
- SaaS providers — Create one tunnel per end customer to reach systems in their private networks or on-premises environments.
- IoT and device manufacturers — Create one tunnel per deployed device, such as a camera, router, sensor, or industrial controller.
- Developer tools and ephemeral environments — Create short-lived tunnels for local development, CI/CD pipelines, and preview environments.
- AI and agent platforms — Create one tunnel per customer to connect AI agents and MCP servers to private resources.
Tunnels for Platforms costs $4.50 per additional tunnel per month. The first 1,000 tunnels in every account remain included at no cost.
Every tunnel that exists in your account counts toward your limit. This includes tunnels that are inactive or have no connected cloudflared replicas. To free up capacity, delete tunnels you no longer need.
Enterprise customers can purchase committed tunnel capacity or usage-based billing. To get started, contact your account team.
To add tunnel capacity to your account:
-
In the Cloudflare dashboard, go to Networking > Tunnels.
Go to Tunnels ↗ -
In the Usage card, select Buy more tunnels.
-
Enter the number of additional tunnels you need.
-
Review the order summary and payment method, then select Activate.
Your new limit appears in the Usage card within a few minutes. Your limit is 1,000 tunnels plus the number of additional tunnels you purchased.
You can increase or decrease the number of additional tunnels, or cancel your subscription, at any time. To manage your Tunnels for Platforms subscription:
-
In the Cloudflare dashboard, go to Manage Account > Billing.
Go to Billing ↗ -
Select Subscriptions.
-
Find the Tunnels for Platforms subscription and change the number of additional tunnels, or cancel the subscription.
Changes do not delete any existing tunnels.
If your limit drops below the number of tunnels in your account, existing tunnels continue to work. Cloudflare blocks new tunnel creation until you delete enough tunnels or purchase more capacity.
When your account reaches its tunnel limit, existing tunnels and their connections are not affected. Requests to create a new tunnel fail until you delete a tunnel or increase your limit.
Tunnels for Platforms only changes the number of tunnels per account. Other Cloudflare Tunnel limits are independent:
| Limit | Default |
|---|---|
| Routes (CIDR routes and hostname routes) per account | 50,000 |
| Virtual networks per account | 1,000 |
| Replicas per tunnel | 25 |
| Published applications per tunnel | Limited by configuration size |
Published applications do not count toward the routes limit. For all limits, refer to Account limits.
When you manage thousands of tunnels, automate the tunnel lifecycle with the Cloudflare API or Terraform:
- Retry with exponential backoff — Retry failed API requests that return
429or5xxstatus codes with exponential backoff and random jitter. Queue create and delete operations rather than sending them all at once. The Cloudflare API also applies rate limits. - Use unique, deterministic tunnel names — For example,
tunnel-<CUSTOMER_ID>-<REGION>. Before you retry a failed create request, check whether a tunnel with that name already exists to avoid duplicate tunnels. - Reconcile regularly — Compare the tunnels in your Cloudflare account with your own records. Delete tunnels that are no longer associated with a device, customer, or environment.
- Delete unused tunnels — Use the tunnel connections API to find tunnels with no active connections. Disconnecting
cloudflareddoes not delete a tunnel. - Pre-create tunnels for latency-sensitive workloads — Creating a tunnel takes a few seconds. If users need a tunnel immediately, keep a pool of pre-created tunnels and refill it in the background.
- Run replicas for production workloads — Run at least two
cloudflaredreplicas per tunnel for high availability.