Cloudflare’s Private Origins capability lets websites and applications use servers on private IP addresses without making those origins publicly reachable. A connector running inside the private network establishes an outbound Cloudflare Tunnel, so requests arriving at Cloudflare can be sent securely to the origin over that connection. This removes the need to expose an origin IP address to the Internet or maintain inbound firewall access for it, while allowing organizations to keep applications in private data centers or cloud networks.
General availability means customers can use Cloudflare services with these private origins in production, rather than treating private connectivity as a separate access-only use case. Traffic can pass through Cloudflare’s network and benefit from its application delivery and security controls, including protection against attacks and web threats, while the backend remains private. The approach also supports routing to private services using Cloudflare’s existing connectivity model, making it useful for organizations that want to put internal or otherwise non-public applications behind Cloudflare without relocating them or opening them to direct public access. The announcement centers on extending Cloudflare’s edge protections and delivery to origins that previously could not be reached through ordinary public-origin connections.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.