⌁EndToEnd

Keep the conversation on the devices in it

EndToEnd is a messenger built to keep message contents on the devices taking part. Direct chats, groups, and files are encrypted before they reach the server, with clear explanations of what the service can still see.

In development · Follow the journey

Illustrative product conceptNot a product screenshot

Meet EndToEnd

Private conversations, clear about their limits

A message passes through a server on its way to someone else. EndToEnd is built around a clear boundary at that stop: the server stores ciphertext, while the devices in the conversation hold the contents and the keys needed to read them.

The application brings that idea into familiar actions. Create an account, find a friend by handle, accept a request, and start talking. Conversations can include reply threads, groups, and files. Safety numbers give participants a way to compare the identity used for a chat.

Clear limits are part of the product. This build supports one device per account. It does not hide the social graph, prevent someone from copying a message, or make a password a replacement for lost device keys. EndToEnd is in development, with its protocol notes and user guide available alongside the application.

A closer look

The ideas
inside the idea.

Explore each feature, the problem it addresses, and where it is in the making.

Every project starts somewhere.

A useful boundary you can understand

When a service holds readable messages, the contents depend on that service’s handling of them. EndToEnd takes a different approach to the message path: seal the contents on the device before sending them, then let the server deliver the encrypted result.

The story behind EndToEnd