Route Public Traffic to Private Applications with Cloudflare

Cloudflare has announced the launch of Application Services for Private Origins in closed beta for eligible Enterprise customers. This new capability allows customers to securely route traffic to private origins without exposing those origins to the public Internet. This means that Cloudflare's security, performance, and programmability services can now protect applications running on private networks, just as they do for public Internet applications.

Key Technical Details

The new capability builds on connectivity patterns Cloudflare already supports today through Cloudflare Tunnel, Cloudflare One Client, and private network integrations. It extends the same model to existing Cloudflare WAN or Cloudflare Mesh connectivity without requiring connector software running on the origin. Customers can define their routing behavior through APIs and the dashboard instead of managing separate networking stacks for each product.

Practical Implications for Developers

With this new capability, developers can now:

• Securely route traffic to private origins without exposing them to the public Internet
• Apply Cloudflare's security, performance, and programmability services to private applications
• Use WAF rules, bot management, rate limiting, caching, rewrites, and Workers in front of private origins without requiring public IP exposure or inbound firewall rules
• Define routing behavior through APIs and the dashboard instead of managing separate networking stacks for each product

This new capability creates a more unified model across Cloudflare products and provides a single source of truth for controlling how private traffic moves through the Cloudflare environment.