Cloudflare makes application services for private origins generally available to Cloudflare One customers
Cloudflare has made generally available a feature that routes public traffic to private origin servers while applying WAF, bot management, caching and Workers. It applies to organisations that already use Cloudflare One connectivity.
What to do now
Cloudflare said on 30 October 2026, in a blog post, that its services for private origins have reached general availability. The idea is to let traffic from the internet reach origin servers that are not publicly exposed, with Cloudflare's network sitting in between.
According to the company, that traffic can use the same services available for public origins: the web application firewall, bot management, caching and Workers for running code at the edge. The feature is open to every customer with Cloudflare One connectivity, the company's networking and access offering.
For teams hosting applications on an internal network or in a data centre without public addresses, this offers a way to publish a service while keeping the origin itself off the internet. The published summary does not cover pricing, supported connection methods or technical limits, so administrators will need Cloudflare's documentation for those details.
What to do now
- Check whether your organisation has Cloudflare One connectivity, which the announcement names as the prerequisite.
- List applications currently exposed directly to the internet that could instead be served from a private origin.
- Review Cloudflare's documentation for connection options, limits and pricing impact, none of which the announcement details.
- Before migrating anything, confirm in a test environment that WAF, bot management and caching rules behave as expected.