Announcing Cloudflare OHTTP Gateway – expanding access to Cloudflare’s privacy-preserving infrastructure
- ID
- 31134
- Status
- summarized
- Published
- 02 Oct 2026, 9:00 PM
- Fetched
- 02 Oct 2026, 10:45 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/announcing-cloudflare-ohttp-gateway/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 5.5
- Created
- 02 Oct 2026, 10:46 PM
- Tags
- Audience
- developersai_ml_learnerssaas_founders
What happened
Cloudflare opened a closed beta for a self-serve OHTTP Gateway, a paid add-on customers enable on their zone to receive Oblivious HTTP traffic without seeing client IP addresses or TLS fingerprints. OHTTP splits requests across two independently operated hops — a relay that blindly forwards encrypted requests and a gateway that decapsulates them — so no single party sees both client identifiers and request contents; Cloudflare also renamed its 2022 'Privacy Gateway' product to 'Cloudflare OHTTP Relay'. Named users of the pattern include Flo Health's app Anonymous Mode and Apple's Private Cloud Compute, which uses OHTTP to disassociate AI inference requests from user identities.
Why it matters
The specific decision: if your servers already sit behind Cloudflare, you previously could not pair them with a Cloudflare-operated relay without collapsing the relay/gateway separation of trust — this gateway is the missing half, so the choice becomes pairing a non-Cloudflare relay with the Cloudflare gateway versus staying with your current setup. Because it is a waitlist closed beta on a paid add-on with no published price, treat it as a watch-list item and do not architect around it this quarter; the actionable step now is deciding whether an IP-free request path is worth a two-hop latency and vendor-pairing cost for any feature where you currently log client IPs. No Malaysia- or SEA-specific detail appears in this text, so the relevance is only as general infrastructure local apps could adopt.
Discussion angle
Who in the room actually needs to stop seeing client IPs — a health, finance, or AI-inference feature — and is a relay/gateway trust split worth the extra hop versus simply dropping the IP at ingest and logging nothing?