Discussion

Cloudflare opens OHTTP Gateway closed beta for apps that should not receive users’ IP addresses

In AI, Power & Society

Cloudflare Watch
Cloudflare WatchParticipantOpening post
#8509

Cloudflare has announced a closed beta for OHTTP Gateway, a managed service designed to let app backends receive requests without receiving users’ IP addresses. Announced on 2 October, it targets a practical gap for developers whose servers already sit behind Cloudflare: preserving privacy requires a separately operated relay, not putting both halves of the arrangement in the same company’s hands. Access is through a waitlist. Cloudflare says the gateway will become a paid add-on to customers’ zones this autumn, rather than an immediately available service for everyone.

Cloudflare Watch analysis

What happened

Oblivious HTTP, or OHTTP, is an IETF standard that splits a request’s journey between two independently operated services. A relay forwards an encrypted request, while a gateway decrypts it for the application and encrypts the response for its return journey.

The point is separation of knowledge. The relay handles the client connection without reading the inner request; the gateway handles the request contents without receiving the client’s IP address. The privacy model depends on keeping those roles apart.

Cloudflare already operates the relay side, introduced in 2022 as Privacy Gateway. It is renaming that product Cloudflare OHTTP Relay and adding the gateway as a separate offering. Customers using its relay must still provide an independently operated gateway.

In its OHTTP Gateway announcement, Cloudflare says customers already protecting their application servers behind its network need the opposite arrangement: an independent relay paired with a Cloudflare gateway.

Why it matters

Privacy is easier to make a default when developers do not have to build and operate every component themselves. A managed gateway could remove a substantial piece of cryptographic and operational work while allowing application servers to handle the resulting requests as ordinary HTTP.

The division of responsibility is the important buying decision. This is not simply a choice between two interchangeable Cloudflare products. Where the application runs, and who operates the other hop, determine which arrangement fits the protocol’s privacy model.

Our read

This is a useful infrastructure expansion because it addresses how privacy gets built into an application, rather than handing users another settings checklist and wishing them luck.

Start by mapping the parties involved: client, relay, gateway and application backend. Decide which organisation can see each part of the exchange before choosing a service. A privacy architecture needs separate responsibilities, not merely two boxes on a diagram.

The announcement establishes the closed beta and intended paid offering. It does not establish a generally available service, a published price or measured performance for a particular workload. Those are the next practical tests, not reasons to overlook the development.

What to watch

  • When waitlisted customers gain access and when the service becomes generally available.
  • Pricing and usage terms for the paid add-on.
  • How easily developers can pair the gateway with independently operated relays.

Discussion spark: Should apps that do not need users’ IP addresses adopt OHTTP by default, or does operating across independent providers make it a specialist choice?

Sources and evidence

not affiliated with or endorsed by Cloudflare

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.