Communication
Talk and work without giving the middle a copy.
Messages, groups, live documents and agent output travel sealed on one connection. Push, mail and video rooms run on the same identity, and this page says exactly where each one leaves the seal.
Live · by request · mail in preview
The relay reads the envelope and never the letter.
A sealed message is encrypted on the device before it leaves. To deliver it, the relay has to know who sent it, who it is for, what kind of thing it is, how big it is and when it came. That is all it gets.
Outside: the relay reads this
- From
- @lena.sorvenna
- To
- @dispatch.sorvenna, a group
- Kind
- message
- Size
- 1.4 kB
- Arrived
- 09:14:07 UTC
Inside: sealed on the device
The words and the attachment. Only the devices that hold the key can open them.
Direct messages and groups are sealed on the device.
Both run on open implementations of published protocols, with the keys of the identity a person already has.
- Direct messages
- One-to-one messages run on libsignal, the open implementation of the Signal protocol.
- Groups
- Group messages run on OpenMLS, the open implementation of the MLS standard (RFC 9420). A member’s key is the key of their identity.
01
Keys
Each device makes its own keys. The private half never leaves it.
02
Seal
The message is encrypted on the sender’s device, for the devices of the people it is for.
03
Carry
The relay passes it on, or holds it sealed while a device is offline.
04
Open
Only a device that holds the key opens it.
Rooms, documents and agent output share one connection.
Chat, presence, documents people edit together and the output of an agent use the connection a device already has open. The SDK seals rooms by default, and an app has to opt out on purpose.
- Rooms and presence
- Who is here, who is typing, and every message in order.
- Live documents
- Several people and agents edit one document, and every change reaches everyone.
- Agent output
- An agent writes its answer once. Every reader gets it as it arrives and can catch up after a break.
Four kinds of traffic leave the seal, and each one is marked.
Some traffic has to reach a network we do not run, or a server that has to read it. This is every kind of traffic, who can read it and where it leaves.
Direct message
Who can read the contentThe two people’s devices
What the middle seesSender, recipient, kind, size and time
Stays sealed
Group message
Who can read the contentThe members’ devices
What the middle seesSender, members, kind, size and time
Stays sealed
Room, live document, agent output
Who can read the contentThe people and agents who hold the room’s key
What the middle seesRoom, sender, kind, size and time
Stays sealed
Push in sealed mode
Who can read the contentThe app that receives it
What the middle seesApple, Google or the browser maker carries it and cannot open it
Stays sealed
Room an app opted out of sealing
Who can read the contentIts members, and the relay
What the middle seesEverything in the room
Leaves at: The relay
Push alert
Who can read the contentThe person, and the push service
What the middle seesThe text of the alert
Leaves at: Apple, Google or the browser maker
Who can read the contentEvery mail server that carries the letter
What the middle seesThe whole letter
Leaves at: Amazon SES in Ireland, then the public internet
Video room
Who can read the contentThe people in the room, and our video servers
What the middle seesAudio, video and a recording when one is made
Leaves at: Our video servers in Helsinki
Notifications follow the sign-in.
Push reaches a person on web, iPhone and Android. A device receives push only while someone is signed in on it, and signing out removes it.
- Three modes
- An alert the system shows, a silent wake for the app, or a sealed message that only the app can open.
- No secrets on a lock screen
- Push refuses to carry a sign-in link or a one-time code it can see.
- No tracking
- Delivery is recorded. Opens are not tracked.
Mail goes out from your own domain.
Send, receive and broadcast from your domain, for people, shared inboxes and agents. Mail exists to reach the public internet, so the servers that carry a letter can read it.
- Your domain
- Publish the DKIM, SPF and DMARC records we give you, and send as yourself.
- Inboxes for everyone
- Addresses for people, teams and agents, with every arriving letter as a thread and a webhook.
- One API
- Templates, audiences, broadcasts, webhooks and SMTP for older apps.
Mail is in preview. It travels through Amazon SES in Ireland today, until our own mail host is live.
Only signed-in people join a video room.
A video room opens for signed-in identities, with invites and recording. Video runs through our video servers in Helsinki and is not encrypted end to end, so keep what must stay sealed in a sealed room.
A late truck at Sorvenna Logistik GmbH, from the group to the customer.
Sorvenna is a made-up freight company. One delay touches four kinds of traffic, and only the last one leaves the seal.
01
Dispatch talks it through
The dispatchers write in a sealed group. The relay sees the members and the sizes, never the route or the customer.
02
An agent answers in the room
The routing agent, an identity like any member, writes a new plan into the sealed room. Everyone reads it as it arrives.
03
The driver gets a push
The new route goes to the driver’s phone as a sealed push. Apple or Google delivers it and cannot open it.
04Leaves the seal
The customer gets a mail
The customer is not on OpenPulse, so the notice goes out as mail from sorvenna.example. Here the words leave the seal.
What a careful buyer asks next.
- Can OpenPulse read our messages?
- Sealed ones, no: the keys are made on your devices and never reach us. We can read a room an app opted out of sealing, mail, and video while it passes our video servers.
- Can an app switch sealing off quietly?
- The SDK refuses to send a room it cannot seal. An app has to opt out on purpose, in its own code, and an organization can require sealed rooms.
- Can we run the relay ourselves?
- Yes. The relay is licensed under AGPL-3.0, and an organization can run its own. The repository is not public yet, so ask for it with your request.
Where it stands today.
- Our use of libsignal and OpenMLS has not been independently audited.
- Live room events are held in memory on one node in Helsinki today.
- Phone numbers for calls and texts on the same identity are planned.
Move your conversations onto a sealed wire.
Tell us who needs to talk and what they build. We open your organization and its rooms with you.