|
Cloudflare announced that its services for private origins are now generally available, giving customers the ability to securely route traffic to their backend infrastructure.
Cloudflare announced the general availability of private origins in a blog post:
Today, Cloudflare services for private origins is generally available. Point a proxied DNS record at a private IP, and Cloudflare reaches the origin over your existing Cloudflare One connection. Your origin stays private, while web application firewall (WAF), caching, bot management, and Workers work just as they do for public origins.
The feature was originally released as a closed beta in June to address feedback from customers:
In June, we launched this capability in closed beta to address a problem we kept hearing from customers: Their internal APIs, AI agent backends, MCP servers, and operational tools weren’t built to face the Internet, but those services still need to accept requests from partners, customers, or agents over the Internet. Before the beta, putting Cloudflare in front of these services meant exposing a public IP, opening a firewall port, or running cloudflared alongside the origin.
The blog goes on to highlight how the feature works: |
