Cloudflare announced general availability for services that route public requests to private origins. Customers can point a proxied DNS record at a private address and carry traffic over an existing Cloudflare One connection.
What the announcement includes
- The origin keeps its private IP rather than needing a publicly reachable address.
- Cloudflare lists WAF, bot management, rate limiting, caching, rewrite rules, and Workers among the services available in the request path.
- The account needs the relevant entitlement and a supported Cloudflare One connectivity option; some services and health-check configurations remain limited.
The release is intended for internal APIs and tools that need controlled access from partners, customers, or agents without turning the origin into a public service.
Before adopting it, verify the account prerequisites and return routing in Cloudflare's documentation. General availability does not mean every network topology or feature is supported.