← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Cloudflare Releases Private Origins for Application Services to General Availability

🔄 Updated 6d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Public traffic can now reach private applications without exposing IPs.
  • Existing Cloudflare security features apply to private origins.
  • Configuration simplified with automatic private IP detection in DNS.
  • Requires Private Origins entitlement and Cloudflare One connectivity.

Private Origins Now Generally Available

Cloudflare has announced the general availability of Application Services for Private Origins. This service allows applications hosted on private networks to receive public internet traffic without needing to expose their internal IP addresses or open inbound firewall ports. The feature was previously in a closed beta since June.

Addressing Customer Needs

According to Enrique Somoza, product development manager at Cloudflare, the capability addresses a common customer problem: internal APIs, AI agent backends, and operational tools that were not designed for direct internet exposure but still require access from external partners, customers, or agents. This service extends Cloudflare's protective measures to these internal services.

Unified Security and Performance

With Private Origins, Cloudflare's existing security and performance features, such as WAF, bot management, rate limiting, caching, and Workers, can be applied to private origins. This provides the same level of protection and control for internal applications as for public-facing ones. The service also supports private TCP/UDP origins via Spectrum and private connectivity for Workers.

Configuration and Requirements

Configuration has been simplified, with private IP addresses automatically detected in proxied DNS records, and private routing configurable through the DNS API. Using Private Origins requires a Private Origins entitlement, Cloudflare One connectivity, and Unified Routing (unless using Cloudflare Tunnel). Cloudflare WAN and Mesh connections also need return routes for specific Cloudflare IPv4 and IPv6 source ranges.

Industry Context

Cloudflare is not unique in offering solutions for connecting public services to private backends. Other cloud providers, such as AWS with CloudFront VPC Origins and Microsoft with similar offerings, also provide comparable functionalities. This trend reflects a broader industry need to secure and manage access to internal infrastructure from external sources.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Cloudflare has made Application Services for Private Origins generally available, enabling public internet traffic to reach applications on private networks without exposing IP addresses or opening firewall ports. This allows internal services to use Cloudflare's security and performance features previously reserved for public-facing applications.