In development
Private communicationwithout unnecessary trust.
Flux is a messenger in early development. Messages are encrypted on your device and can be read only on the recipient's device. The servers in between carry data they cannot read.
- End-to-end encryption
- Implemented
- Transport independence
- Experimental
Live demo
Runs in your browser
What the network sees
Ciphertext appears here.
Recipient reads
Meet at 9 by the north gate.
Product
A messenger built around what it does not need to know.
- Implemented
Encrypted conversations
One-to-one messaging protected by end-to-end encryption.
- Planned
Identity without a phone number
Accounts are based on keys you control rather than a phone number or email.
- Planned
Encrypted attachments
Files and media protected with the same guarantees as messages.
- Research
Offline mesh delivery
Device-to-device delivery when there is no internet connection.
How it works
Encrypted before it leaves your device.
The message is readable only on the two devices. Everything between them handles ciphertext it cannot read.
06 steps · press play
Sender device
Sees plaintext
01User A
Writes a message on their own device.
Readable message: “Meet at 9 by the north gate.”
02Encryption
The message is encrypted end-to-end before it is sent.
Implemented
Network
Sees ciphertext only
03Flux Network
Relays encrypted payloads without access to their content.
PlannedEncrypted message: 8f3c 1a9e 77d0 c4b2 09e5 f1a8 3d6c b207 5e91 a4c3 …
04Transport
Delivery is not bound to a single server or network path.
Experimental
Recipient device
Sees plaintext
05User B
Receives the encrypted payload.
06Local decryption
Only the recipient's device can decrypt the message.
ImplementedReadable message: “Meet at 9 by the north gate.”
Security
What Flux protects, and how far along each part is.
Every capability is labelled with its real state. Research and planned work are never presented as finished.
5 of 5 capabilities
End-to-end encryption
Messages are encrypted on the sender's device and can only be decrypted by the recipient.
ImplementedUser-controlled identity
Your identity keys are generated and held by you, not issued by a server.
PlannedEncrypted local storage
Message history stored on your device is encrypted at rest.
PlannedMinimal server knowledge
Servers are designed to learn as little as possible. No message content, minimal metadata.
PlannedTransport independence
Communication does not depend on a single server, provider or network.
Experimental
- Implemented
- Works in the current build.
- Experimental
- Working prototype; may change.
- Research
- Being investigated; not built yet.
- Planned
- On the roadmap; work not started.
Transport
Encryption first. Transport second.
Because messages are encrypted end-to-end, the path they take does not need to be trusted. Flux treats transports as interchangeable carriers.
End-to-end encrypted message
Encrypted on the sender's device. No transport can read or change it.
Online
Delivery over the internet through Flux relays.
ExperimentalMesh
Nearby devices pass encrypted messages to each other without the internet.
ResearchPluggable transports
Additional carriers can be added without changing the encryption layer.
Planned
Early access
Join the Waitlist
Be among the first to use Flux. We send one email, when your invite is ready.
Your email is used only for the invite. See the Privacy Policy.