Cloudflare has launched Application Services for Private Origins in closed beta, aimed at eligible Enterprise customers. The feature lets customers route public traffic to private origins without exposing those origins to the public Internet, so Cloudflare's WAF, bot management, rate limiting, caching, rewrites, and Workers can sit in front of private networks the same way they do for public-facing applications. No public IP exposure, inbound firewall rules, or cloudflared running on the origin are required.
The company's argument is that the divide between public and private infrastructure is eroding. Many applications organizations depend on are not public websites but internal APIs, AI agent backends, MCP servers, and operational tools that were never meant to face the Internet, yet they still need the same security and performance services. Applying those services previously meant public IPs, firewall exceptions, connector software, or other networking workarounds.
Building on the existing private networking layer
The capability extends connectivity Cloudflare already supports through Cloudflare Tunnel, Cloudflare One Client, and private network integrations. Tunnel has long routed public traffic to private applications via cloudflared; the new model brings the same result to existing Cloudflare WAN (IPsec, GRE, CNI links) or Cloudflare Mesh connectivity without connector software on the origin. Cloudflare's private networking routing layer handles how traffic reaches private destinations across Tunnels, Virtual Networks, Mesh, and other models, and customers configure that behavior through APIs and the dashboard rather than separate stacks per product.
Because the private networking layer is now wired into the application services stack, private IPs become valid origin targets for public hostnames. Workers VPC bindings and Spectrum private origin routing rely on the same underlying layer, giving customers a single control point for private traffic.
Cloudflare frames the model as four combinations of user location and application location:
Public users reaching public applications is what Cloudflare has always done, and Cloudflare One covers private users reaching public services. Public-to-private is what ships now; private-to-private is the next target.
How routing works
Previously, reaching a private origin meant tradeoffs: Cloudflare Tunnel with a connector near the origin, or Cloudflare Load Balancing with private origin pools for health checks and failover—often alongside parallel infrastructure such as public-facing load balancers, reverse proxies, mTLS between hops, and multi-layer TLS termination.
Operationally, the feature is a toggle. Turning on Use private network routing for a proxied A or AAAA record leaves WAF, rate limiting, caching, bot management, and transform rules running as usual on Cloudflare's network. Only the final hop changes: the connection takes the customer's private network connectivity instead of the public Internet.
The toggle is enabled automatically for RFC 1918 private IPv4 ranges (10.x.x.x, 172.16.x.x–172.31.x.x, 192.168.x.x), RFC 6598 CGNAT ranges (100.64.x.x–100.127.x.x), and RFC 4193 Unique Local IPv6 Addresses (FC00::/7), since those addresses are only reachable inside private networks. For public IPs reachable only through a private network or tunnel, it must be enabled manually.

The API surface
For API-driven deployments, private routing is an extra attribute on a standard DNS record.

Inside Cloudflare, the proxy platform resolves where to send traffic for app.example.com by querying Cloudflare's Origin API, whose response carries metadata indicating a private network path:
POST /zones/{zone_id}/dns_records
{
"type": "A",
"name": "app.example.com",
"content": "10.0.0.50",
"ttl": 300,
"proxied": true,
"use_private_routing": true
}
The use_private_routing flag drives the decision. When the proxy sees it, it hands the request to the private networking layer instead of connecting to the private IP over the public Internet. That layer routes the connection over whatever connectivity the customer already has: IPsec, GRE, Cloudflare Tunnel, CNI, or Cloudflare Mesh.
Layer 4 and Workers reach the same origins
The model is not limited to HTTP. An origin can be a TCP database, a UDP logging endpoint, or a private API that Workers call directly. Spectrum, Cloudflare's Layer 4 proxy, can now front TCP and UDP services on private IPs by specifying a virtual_network_id on the origin configuration rather than creating a load balancer pool as an intermediary:
{
"zone_name": "example.com",
"ipv4_addresses": ["10.0.0.50"],
"use_private_routing": true
}
When a Spectrum application is created or updated with a private origin and virtual network, Cloudflare verifies the IP matches a route in the customer's Cloudflare Tunnel before saving; if no matching route exists, the API rejects the request and the application is not created. Once saved, Spectrum hands the connection to the virtual network, which routes it through the associated tunnel on the same path HTTP traffic uses. In this initial release, Spectrum private origins are supported through Cloudflare Tunnel only, with other connectivity options to follow. The service stays private, with no public IP, connector software, or load balancer.
For Workers, a VPC binding instructs the runtime to use the same private path as DNS records, so browsers, mobile apps, Workers, and AI agents can all reach private origins through Cloudflare.
Availability
Public-to-private routing is in closed beta, with General Availability targeted for Q4 2026. After GA, Cloudflare says it will build toward private-to-private flows, in which users, services, and AI agents on private networks reach applications on other private networks with Cloudflare's application services in the middle. The stated end state is uniform protection: an employee on Cloudflare One Client reaching wiki.company.internal gets the same WAF, rate limiting, and bot management as a customer hitting a public API, and an AI agent consuming an internal API passes through the same stack as a browser.
Access requests go through Cloudflare account teams. Setup requires Cloudflare One connectivity (IPsec, GRE, CNI, or Cloudflare Mesh) and a return route for Cloudflare's source IP range 100.64.0.0/12 in the private network, and is documented in Cloudflare's DNS developer documentation.



