Skip to content
INTERNET INFRASTRUCTURE & NETWORKS

Cloudflare Announces General Availability of Services for Private Origins, Bringing Enterprise Security to Internal Infrastructure

Cloudflare has officially announced the general availability of its application services for private origins, a major milestone that allows organizations to route public traffic directly to private internal infrastructure through existing Cloudflare One connections. The launch removes a longstanding architectural hurdle for enterprise teams, making it possible to secure internal APIs, AI agent backends, Model Context Protocol (MCP) servers, and operational tools with the same robust suite of controls used for public-facing websites.

With this general availability release, administrators can point a proxied DNS record at a private IP address, enabling Cloudflare to handle incoming requests securely without exposing those services directly to the public Internet. Crucially, web application firewall (WAF) rules, caching layers, bot management systems, and Cloudflare Workers can now operate seamlessly on private origins just as they do on public ones, giving enterprise technology teams unprecedented flexibility in how they design and protect their internal network perimeters.

Addressing the Private Infrastructure Challenge

The journey to this general availability release began earlier in the year when Cloudflare launched the capability in a closed beta program. Throughout customer consultations and deployment reviews, Cloudflare engineering teams repeatedly heard a common frustration: modern enterprise infrastructure—such as internal microservices, proprietary AI backends, and operational dashboards—was never designed to face the open Internet. Yet, these exact systems frequently needed to accept legitimate requests from external partners, customers, or automated agents.

Before the introduction of private origins routing, closing this operational gap required complex and often risky workarounds. Organizations typically had to resort to exposing a public IP address, manually punching holes through perimeter firewalls, or running specialized connector software like cloudflared directly alongside the origin server. These legacy requirements frequently meant that internal applications were left operating without the sophisticated protections and performance controls typically reserved for public-facing digital assets. Essential security measures such as WAF protection, bot mitigation, advanced rate limiting, traffic acceleration, smart caching, and custom request rewrites were difficult or impossible to apply uniformly across internal systems.

What is Generally Available Today

Following the conclusion of the closed beta period, during which eligible organizations requested access via their dedicated account teams, Cloudflare is opening the feature up broadly to its customer base. Organizations can now point a proxied A or AAAA record directly at a private IP address, instantly bringing Cloudflare’s comprehensive suite of application services to internal origins.

While the release unlocks significant architectural flexibility, a few specific limitations remain in place. Features such as Argo Smart Routing and Dedicated CDN Egress IPs are not currently supported under this configuration, and origin health checks require the use of Cloudflare Load Balancing. Despite these minor boundary conditions, the core operational advantages are immediate. The origin server retains its native private IP address without requiring any inbound firewall exceptions. Depending on the chosen network architecture, using Cloudflare WAN eliminates the need to install connector software directly on the origin, while Cloudflare Mesh allows a single connector running within the private network to efficiently serve multiple origins.

Understanding the Request Flow and Technical Implementation

The underlying architecture of private origins routing is designed to integrate cleanly into existing enterprise network environments. When an administrator creates a proxied A or AAAA record pointing to a designated private IP address, private network routing is enabled automatically for supported private IP ranges. This includes standard 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 security and stability reasons, this automatic activation cannot be disabled for these specified ranges through the API. If an organization utilizes a public IP address that is exclusively reachable via their private network, the private routing setting can also be enabled manually.

Cloudflare services for private origins is now generally available

The overall request lifecycle remains remarkably consistent with standard web traffic processing. TLS termination, WAF execution, rule evaluation, and caching operations continue to run seamlessly across Cloudflare’s global network. When an API call is made to create or manage a DNS record through Cloudflare’s infrastructure, private routing functions simply as an additional configuration attribute on a standard DNS record, signaling the platform to handle the destination accordingly.

Behind the scenes, Cloudflare’s proxy platform resolves traffic destinations by querying the internal Origin API, which returns metadata indicating that the target should be reached via a secure private network path rather than the public Internet. When the proxy encounters this distinct flag, it bypasses direct public routing attempts and hands the connection off to Cloudflare’s private networking layer. This layer then safely bridges the traffic across the customer’s established private network connectivity methods, whether the organization relies on IPsec tunnels, GRE tunnels, Cloudflare Tunnel, Cloudflare Network Interconnect (CNI), or Cloudflare Mesh.

Getting Started and Best Practices

Organizations looking to implement private origins routing must ensure they have an active Cloudflare One connection established, alongside a properly configured private IP address for their origin server. The setup process involves creating a proxied A or AAAA record for the private IP and verifying that the private network routing preference is active. Once configured, all existing WAF policies, caching rules, and bot management protocols apply automatically to the designated hostname without requiring additional reconfiguration.

Early deployment feedback from the closed beta phase highlighted a critical troubleshooting tip for system administrators: if incoming requests result in timeouts and fail to reach the origin, the return route should be inspected immediately. Engineers noted that a missing or misconfigured return route for Cloudflare’s source IP ranges was the most frequent setup hurdle encountered during initial deployments. Comprehensive documentation is available through Cloudflare’s official developer resources to guide teams through the complete configuration workflow.

Looking Ahead to Private-to-Private Connectivity

While today’s general availability release focuses primarily on safely directing public traffic toward private origins, Cloudflare’s engineering roadmap extends well beyond the perimeter. Development is already underway on the next phase of the project, which will tackle private-to-private traffic routing. This upcoming capability aims to allow users, internal services, and specialized AI agents residing on private networks to securely reach applications located on entirely separate private networks, all mediated through Cloudflare’s unified application services.

Engineering efforts for private-to-private routing are progressing steadily, with a closed beta targeted for early adoption. Organizations interested in participating in future testing phases are encouraged to coordinate directly with their account teams. The ultimate strategic goal is to ensure that all private applications—such as an internal corporate wiki accessed by employees or service-to-service microservice communications spanning multiple cloud providers and data centers—can benefit from enterprise-grade security controls, even when the traffic never touches the public Internet. For now, today’s release successfully bridges the gap, bringing trusted WAF, caching, bot management, and Worker capabilities to private origins over infrastructure that organizations already operate and control.