Skip to content
OpenE2EE
Sign inStart free

Encrypted delivery

OpenE2EE Signal Protocol Relay is the delivery half of an end-to-end encrypted application.

Ship fully featured end-to-end encrypted messaging, securely, and at scale. Run encrypted device mailboxes, zero-knowledge group credentials, group fan-out, attachment storage, and device push wake notifications without running delivery infrastructure. The SDK runs on each device and reaches Relay through one connection URL.

The Signal Protocol Relay stores ciphertext and the account, device, route, timing, size, quota, and abuse metadata that delivery requires. The relay never needs message plaintext or device private keys.

Start free No credit card neededRead the quickstart

Free

$0

  • 100 Relay MAU
  • 100,000 delivery units
  • 1 GB storage

Production roots, hard capacity caps, and no automatic charge.

Compare every plan

What Relay holds

A mailbox for each device, not one for each account. A device that has been offline for a week pulls what it missed, and a device added today receives what is sent from that moment.

What the Signal Protocol Relay holds: one sealed mailbox for each device On the left, an outlined device with readable content bars and a filled private key. A dotted rule marked seal stands between it and the relay. The relay is a pair of open brackets holding three solid slabs, each carrying metadata ticks along its top edge: one sealed mailbox for each device. A second dotted rule marked open stands between the relay and two more outlined devices, each with its own readable content and its own private key. device · sealssealopen metadataSignal Protocol Relay devices · pull
The application seals on the device. Relay stores and routes the sealed envelope, and the metadata ticks are what it reads to do that: the account, device, route, timing, size, quota, and abuse metadata delivery needs.

What Relay operates

Delivery
Durable encrypted device mailboxes, pull, acknowledgment, expiry, and multi-device fan-out.
Groups and files
Bounded group fan-out and private encrypted attachment storage. Customer application servers do not need to become message infrastructure.
Operations
Push wakes, exact usage, quotas, lifecycle controls, recovery drills, and an operator plane.
Your application
Authentication choice, product directory and social graph, user experience, moderation policy, recovery policy, and application data.

The OpenE2EE Signal Protocol SDK works with the Signal Protocol Relay or another adapter. The Signal Protocol Relay is the shortest hosted path, not a requirement of the SDK. A self-hosted adapter keeps relay metadata in infrastructure the developer operates. A managed project places the required relay metadata with OpenE2EE.

Plans, meters, and overageRelay service termsCompare architecture with Virgil SecurityReview SDK licensing

One connection for each environment

The connection URL is public configuration, not a credential. The SDK resolves the exact environment and project binding from that URL.

Development
Every project opens one automatically, with isolated state and credentials. oe dev writes its connection.
Production
oe deploy writes the production connection. Production roots and hard capacity caps, with no automatic charge on the free plan.
One variable
Both write OPEN_E2EE_RELAY_URL, so the application source does not change between them.
No pairing step
You do not select a Relay hostname or pair it with a second key.

Read the Relay quickstartStart a Relay project