OpenE2EE Signal Protocol Relay Beta Service Limits
The launch boundary for capacity, support, and service commitments.
The Relay terms incorporate this document. The permanent copy of this version is at /legal/relay-beta-limits/2026-09-10.
Service status
Relay remains a beta until OpenE2EE announces general availability. The Development environment and Free production plan have no service-level agreement. Paid beta support and operational controls are those shown in the order. No uptime credit, response-time commitment, data residency promise, BAA, or production recovery objective applies unless a signed order form states it.
Plan and protocol limits
The current plan capacities and exact meter definitions are at Relay pricing. All plans support the same Relay protocol capabilities. A plan does not unlock or remove groups, attachments, sealed sender, multi-device delivery, or push wakes.
- Direct encrypted envelope: 256 KiB maximum.
- Mailbox: 3,000 accepted messages maximum.
- Group encrypted body: 96 KiB plus a 512-byte prefix.
- Group delivery: up to 5,000 destination devices in 100-destination fan-out pages.
- Attachment upload URL: never more than 15 minutes. The current window is shorter.
- Completed attachment retention: 30 days maximum.
Capacity and change control
A hard cap rejects new work without changing already accepted encrypted content. OpenE2EE can reduce abusive or unsafe traffic, repair a service incident, or change pre-release limits with reasonable notice when practicable. A material paid-plan change applies under the accepted service terms and recorded order.