Cloudflare private origins goes GA: WAF and caching for internal APIs and MCP servers

Cloudflare Blog · rss · 2026-10-30

Cloudflare's services for private origins is now generally available. Point a proxied DNS record at a private IP and Cloudflare reaches the origin over existing Cloudflare One connectivity (IPsec, GRE, Tunnel, CNI, or Mesh)—no public exposure or firewall ports needed. Internal APIs, AI agent backends, and MCP servers can now get the same WAF, caching, bot management, rate limiting, and Workers controls as public apps. Private routing auto-enables for RFC 1918/CGNAT/ULA ranges; the most common beta failure was a missing return route for Cloudflare's source ranges. Private-to-private traffic is next, targeting closed beta in early 2027.

Original post →

More from coding & agent

coding & agent channel →