· javascript

Cloudflare Introduces Private Origins for Application Services

Private-to-private connectivity is not yet supported.


Announced in closed beta in June, the service is now generally available with a simplified configuration: private IP addresses are automatically detected in proxied DNS records, and private routing can be configured through the DNS API. Enrique Somoza, product development manager at Cloudflare, writes: We launched this capability (...) 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.

Existing Cloudflare connectivity can be used to apply WAF, bot management, rate limiting, caching, and Workers to private origins, just as with public-facing applications. The service also supports private TCP/UDP origins through Spectrum and private connectivity for Workers.

Earlier coverage

Related coverage

Also worth reading

  1. next.js 16.5.0-canary.53 released
  2. uBlock Origin, Firefox, suffers Universal XSS from element picker
  3. nextest coding agents design install scripts
  4. datasette-maplibre 0.1a0
  5. datasette 1.0a43