Announcing Cloudflare OHTTP Gateway – expanding access to Cloudflare’s privacy-preserving infrastructure

Cloudflare is launching a closed beta of its OHTTP Gateway, a managed service designed to help developers receive HTTP requests without learning users’ IP addresses or other identifying network metadata. Based on the IETF’s Oblivious HTTP standard, OHTTP separates traffic through independently operated relays and gateways: relays see client identifiers but not encrypted request content, while gateways decrypt requests for application servers without seeing the client’s identity, creating a double-blind privacy model. The new gateway complements Cloudflare’s renamed OHTTP Relay, formerly Privacy Gateway, and gives developers whose applications run behind Cloudflare or receive traffic from third-party relays an option that preserves this separation of trust. Deployed across Cloudflare’s global edge network, the service aims to reduce latency and operational complexity by automatically scaling, managing HPKE encryption keys, supporting standard and chunked OHTTP, allowing ordinary HTTP traffic alongside OHTTP, and integrating Cloudflare Access policies to authenticate relays. To prevent Cloudflare from operating both sides of an OHTTP exchange, the gateway will reject requests originating from Cloudflare Workers or proxied Cloudflare hosts, while developers remain responsible for avoiding personally identifying information within request bodies.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.