Platform Security
Cloudflare Lets Private Apps Accept Public Requests Without Exposing Infrastructure
The company has rolled out general availability for Private Origins, enabling internet-facing traffic to reach applications on private networks while keeping IP addresses and firewall rules hidden.
InfoQ
Cloudflare has moved its Application Services for Private Origins out of beta and into general availability, offering organizations a way to route public internet traffic to applications sitting behind private networks—without revealing their IP addresses or requiring inbound firewall openings.
The feature answers a recurring customer request: internal APIs, AI agent backends, and operational tools that were never designed for public exposure still need to accept requests from external partners, customers, and agents. Private Origins extends Cloudflare's existing security and performance tooling—WAF, bot management, rate limiting, caching, and Workers—to these otherwise-internal services.
How It Works#
When enabled, Cloudflare automatically detects private IP addresses in DNS records marked for routing through the platform, then applies the configuration through its DNS API. The service runs on top of existing Cloudflare connectivity infrastructure, meaning organizations using Cloudflare One, Tunnel, or WAN/Mesh connections can activate it without deploying additional connector software.
The technical foundation requires Unified Routing (except when using Cloudflare Tunnel), a Private Origins entitlement, and return routes configured for Cloudflare's IPv4 (100.64.0.0/12) and IPv6 (2606:4700:cf1:5000::/64) ranges.
What Changes for Security Posture#
The innovation inverts a long-standing network security principle: for decades, IT teams assumed that anything answering to a public DNS name must be reachable from the internet. Private Origins breaks that assumption by allowing private applications to respond to public DNS queries while remaining isolated from direct internet access. Cloud consultant Simon Painter notes the deeper implication: existing WAF, caching, and bot management policies apply automatically, so private applications gain the same protections as public ones—a departure from past practice where internal services often lacked those controls.
Broader Market Context#
Cloudflare is not alone in closing this gap. AWS offers CloudFront VPC Origins for similar use cases, while Microsoft provides comparable functionality through and Private Link.

