OHTTP Relay
integration.
The public technical surface for the limited-availability private beta. Detailed configuration is provided directly during onboarding.
Relay model
ohttp.io provides an Oblivious HTTP relay. The relay accepts an encrypted OHTTP message from a client and forwards it to the customer's configured gateway. It does not decrypt the encapsulated HTTP request or fetch the inner target.
The client obtains the gateway's OHTTP key configuration from the gateway and encrypts the encapsulated request for that gateway before sending it through the relay.
Integration
Private-beta relay routes are provisioned individually. We'll work with you to confirm the gateway, authentication requirements, geography and test flow before going live.
The ohttp.io Relay supports authenticated forwarding to protected customer gateways, including mutual TLS where appropriate.
Privacy boundary
The relay handles the client-facing connection and encrypted OHTTP message, but does not hold the gateway's decryption key. The gateway handles the encapsulated request after receiving it from the relay rather than directly from the original client.
Privacy Pass
The ohttp.io Relay includes Privacy Pass support for relay authentication and abuse control. During private beta, availability and configuration are agreed as part of the integration rather than presented as a universal production-service feature.
Private beta
ohttp.io is currently in limited availability. Detailed endpoint and integration information is shared directly with accepted beta customers rather than publishing internal deployment details here.