Cloudflare has officially announced the general availability of its application services for private origins, a major milestone following a closed beta period introduced earlier this year in June. The new capability allows organizations to point a proxied DNS record directly at a private IP address, enabling Cloudflare to reach the origin over an existing Cloudflare One connection.
This development means that sensitive internal infrastructure—such as internal application programming interfaces, artificial intelligence agent backends, Model Context Protocol (MCP) servers, and critical operational tools—can now benefit from Cloudflare’s robust suite of edge security and performance features without needing to be exposed directly to the public Internet. Historically, these private services were built for internal consumption and were never designed to face the open web. However, as modern architectures evolve, many of these systems must accept incoming requests from external partners, customers, or distributed AI agents over the Internet.
Before the introduction of private origins routing, organizations wishing to place Cloudflare in front of internal resources faced a cumbersome set of architectural hurdles. Teams typically had to expose a public IP address, punch holes through inbound firewalls, or run dedicated connector software like cloudflared directly alongside the origin server. Consequently, these operational friction points meant that countless private applications were forced to operate without the advanced protections and performance controls traditionally reserved for public-facing web applications. They lacked access to critical features such as the web application firewall (WAF), bot management, rate limiting, advanced caching, traffic acceleration, custom rewrites, and Cloudflare Workers.
What is Generally Available Today
During the initial closed beta phase, eligible customers were required to request access through their dedicated account teams to test the functionality. With today’s general availability rollout, Cloudflare is expanding access beyond that initial group, making the feature widely available to organizations looking to secure their private networks.
By pointing a standard proxied A or AAAA record at a private IP address, administrators can immediately leverage Cloudflare’s core application services. The origin server retains its private IP address, and critically, no inbound firewall exceptions are required to facilitate the connection. Depending on the chosen network architecture, deployments utilizing Cloudflare WAN do not require any connector software running directly on the origin. Meanwhile, setups using Cloudflare Mesh rely on a lightweight connector running within the private network that can seamlessly serve multiple origins.
Despite the broad expansion, some technical limitations remain in place for this initial general availability release. Features such as Argo Smart Routing and Dedicated CDN Egress IPs are not currently supported, while origin health checks require the use of Cloudflare Load Balancing. Comprehensive details regarding current platform boundaries and limitations remain available through Cloudflare’s official developer documentation.
How Private Network Routing Works
The mechanics behind the feature are designed to integrate smoothly into existing administrative workflows. Administrators simply create a proxied A or AAAA record pointing directly to their internal origin. For supported private IP ranges, the system automatically enables private network routing. This includes RFC 1918 private IPv4 addresses, RFC 6598 Carrier-Grade NAT (CGNAT) addresses within the 100.64.0.0/10 range, and RFC 4193 unique local IPv6 addresses in the fc00::/7 block. For these designated ranges, the setting is mandatory and cannot be disabled; attempts to turn it off via the API will return an error. If an organization uses a public IP address that is exclusively reachable through a private network, the private routing setting can also be enabled manually.
Once configured, the overarching request flow remains consistent with standard web traffic. Services like Transport Layer Security (TLS) termination, WAF evaluation, rulesets, and caching continue to execute seamlessly across Cloudflare’s global edge network.

For teams automating their infrastructure deployments through the API, private routing functions as an additional attribute embedded within a standard DNS record modification. Behind the scenes, Cloudflare’s proxy platform determines the appropriate destination for a given hostname by querying the internal Origin API. The resulting system response includes specific metadata indicating that the target destination should be reached through a designated private network path rather than the public Internet.
This private_routing flag acts as the primary architectural signal. When Cloudflare’s proxy platform encounters the flag, it bypasses any attempt to connect directly to the private IP address over the public Internet. Instead, the connection is handed off to Cloudflare’s private networking layer, which safely routes the traffic across the organization’s existing private connectivity infrastructure—whether that involves IPsec, GRE tunnels, Cloudflare Tunnel, Cloudflare Network Interconnect (CNI), or Cloudflare Mesh.
Getting Started and Implementation Considerations
To begin leveraging private origins, organizations must ensure they have an active Cloudflare One connection established and a properly configured private network path. Administrators can then create a proxied A or AAAA record for their private IP and verify that private network routing is active. Pre-existing configurations for WAF, caching, and bot management will apply to the designated hostname without requiring additional reconfiguration.
Early feedback from beta participants highlighted one crucial operational detail: if incoming requests result in timeouts and fail to reach the origin, administrators should audit their return routes first. According to Cloudflare engineering teams, a missing return route for Cloudflare’s source IP ranges was the most frequent setup failure encountered during the beta period. Comprehensive setup guidance remains accessible via the developer documentation portal.
Looking Ahead to Private-to-Private Traffic
While today’s release focuses primarily on enabling public traffic to securely reach private origins, Cloudflare is already actively developing the next phase of the project: private-to-private traffic routing. This upcoming capability aims to allow users, services, and artificial intelligence agents operating within private networks to reach applications hosted on entirely separate private networks, all mediated securely through Cloudflare’s application services.
Engineering work for private-to-private routing is currently underway, with a closed beta targeted for early 2027. Organizations interested in participating in the upcoming beta phase are encouraged to coordinate directly with their account teams.
The long-term vision for the platform is to extend the same advanced security protections and administrative controls enjoyed by public web properties to internal applications as well. For instance, an internal employee accessing an internal corporate wiki could soon benefit from granular rate limiting, WAF inspection, and bot management protections. Similarly, service-to-service communication traversing different cloud environments and physical data centers could leverage these same protective controls without ever exposing endpoints to the public Internet.
For now, the general availability release brings essential edge protections—including WAF, caching, bot management, and Workers—directly to private origins, operating over the private network infrastructure organizations already maintain. Organizations with questions or feedback are encouraged to participate in the ongoing discussions on the Cloudflare community forums or reach out to their account representatives.