Privacy beyond the connection.
Encryption protects conversation content across the network, rather than only protecting the connection to a server.
Your conversations.
Your infrastructure.
Message and call other Brax Wink users through the Brax Phone app. End-to-end encryption keeps the conversation between its participants. Self-hosting will let you choose who runs the network, too.
Encrypted messages & callsZero-knowledge architectureSelf-hosting · coming
01 / ZERO-KNOWLEDGE ARCHITECTUREYour conversations.
Your conversations.
Kept on your devices.
Brax Network is designed to carry your conversations without storing them on a server. Whether you use the Brax-hosted network or your own instance, your communication belongs on your devices. Private keys are generated and kept on each device. The server publishes public key bundles so devices can establish encrypted sessions. Conversation history stays on your devices.
Don’t hand the host your secrets.
The design does not rely on the server operator keeping a copy of your private keys safe. Decryption belongs at the participating devices.
No server-side conversation history.
Use Brax’s infrastructure or host your own. The architecture keeps your conversations with the people participating in them.
02 / THE ENCRYPTION LAYERPrivate by design.
Private by design.
Built on open protocols.
Different conversations call for different cryptographic tools. Brax uses OMEMO for messages and DTLS-SRTP for voice key agreement.
OMEMO
A conversation for its participants.
OMEMO protects one-to-one and group chats with end-to-end encryption using AES-256. Your message is encrypted for the participating devices, so your words stay between you and your recipients.
Read the OMEMO specification ↗DTLS-SRTP
Agree on keys. Then speak privately.
DTLS-SRTP agrees on keys between the call endpoints with a DTLS handshake, then encrypts the voice media with SRTP. Each side’s certificate fingerprint is exchanged when the call is set up and checked during the handshake, which helps detect an intercepted key exchange.
Read about DTLS-SRTP ↗03 / A NETWORK OF PEOPLEConnected.
Connected.
On your terms.
Join the Brax-hosted network. Or run a separate instance for your community, team or circle. Open instances can communicate with each other. A closed instance keeps communication within its own boundary.
Open · connects with other open instances Closed · communication stays inside
Hover, focus or tap a device to trace its connections.
Your phone. Your network.
How will I use Brax Network on my phone?
Through the Brax Phone app, currently in development and designed for the Brax Wink device. It will bring private messages, group chats and encrypted voice calls together in one place.
Do I need to run my own server?
No. You can use the Brax-hosted network. Self-hosting will be an option for people who want to operate their own instance for a community, team or private circle.
Can my own instance communicate with Brax Network?
Yes, if you choose an open instance. It can communicate with other open instances, including Brax Network. Choose a closed instance to keep conversations within your own group.
Will the app and server be open source?
Yes. Both the client and server will be fully open-sourced. The repositories will be shared publicly upon release of the service, so you can inspect the code and host your own infrastructure.
What makes it different from Signal?
Both focus on end-to-end encrypted communication. Brax Network adds the choice to run your own instance: open to the wider network, or closed to your own users. Signal’s consumer service does not offer self-hosted instances that connect to its network.
When can I start using it?
The Brax Phone app and network service are in development. App availability, public repositories and self-hosting instructions will be shared with the service release.