01 · Client
Encrypts for the gateway
Encapsulates the HTTP request using the gateway's OHTTP key configuration.
Limited-availability private betaIndependent OHTTP
Independent OHTTP
Relay Infrastructure.
Separate the request from the requester with independently operated Oblivious HTTP relay infrastructure. The ohttp.io Relay forwards encrypted OHTTP messages without decrypting the encapsulated HTTP request.
Join the betaHelp shape the
Help shape the
ohttp.io OHTTP Relay.
We're onboarding a limited number of private-beta customers while we work directly with them on deployment, integration and testing. Relay infrastructure is provisioned appropriate to your geography.
Latest newsLatest OHTTP and ohttp.io news →
ohttp.io opens private beta for its independent OHTTP Relay
The relay stack is operational. We're inviting developers and organisations with real-world Oblivious HTTP use cases to test the service and help shape what comes next.
How it worksSeparate network identity
Separate network identity
from the encapsulated request.
The client encrypts its HTTP message for the gateway and sends the encapsulated request through a relay. The relay sees the client connection and forwards ciphertext, but cannot decrypt the encapsulated HTTP message. The gateway decrypts the message after receiving it from the relay rather than directly from the original client.
02 · ohttp.io Relay
Forwards blind
Forwards the encrypted OHTTP message without decrypting the encapsulated HTTP request.
03 · Gateway
Decapsulates
Handles the encapsulated request without receiving a direct client connection.
Why ohttp.io
Independent by design.
Separation
One side of the flow
When ohttp.io provides the relay, the gateway remains under the control of the customer or another independent operator. We do not operate both sides of the same customer's OHTTP flow.
Privacy
We measure the relay. We don't read the request.
We retain the operational and accounting information necessary to operate, secure and measure the service — not the plaintext encapsulated HTTP request.
Pre-GA
Hands-on by choice
We'll understand your use case, provision the right relay deployment and work with you on integration and testing. Self-service account management and usage analytics are being built for the customer experience.
Something missing?Help shape
Help shape
ohttp.io.
We're building ohttp.io around real problems, not a checklist of features we think people might want.
If there's something you need from an OHTTP relay that you don't see here, tell us. A feature, an integration, a deployment requirement — or something we haven't thought of yet.
Commercial
Private beta first. Pricing before GA.
Commercial pricing will be announced ahead of General Availability. Private-beta participants will receive additional service credit for supporting the development of ohttp.io.