Encrypted messages
Small encrypted envelopes can remain in the sender's outbox or be replicated within configured queue limits across available nodes until the recipient returns.
QEYET / How it works
Private by architecture
A messenger built around devices, not a central inbox.
QEYET gives each browser a cryptographic identity, encrypts content before transport, and uses direct peers plus available mini-nodes to move encrypted envelopes.
Create a device-controlled identity
A standard user chooses an optional display name and receives six recovery words. No phone number or email address is required to create the identity.
Connect in one step
Share an invite code or QR code. The recipient accepts it and QEYET establishes the contact and cryptographic material needed for private delivery.
Encrypt before routing
The sender's device encrypts the message for authorized recipient devices. Routing nodes receive encrypted envelopes rather than readable chat content.
Use the best available path
QEYET prefers direct, low-latency connections when both peers are available. Encrypted messages can also queue locally or travel through available federation and mini-nodes.
Decrypt and acknowledge
The recipient device decrypts the envelope and returns delivery or read state. Status reconciliation corrects stale “waiting” labels when acknowledgements arrive later.
Keep history under device control
Readable history is stored locally. Linked devices and user-initiated encrypted backups provide continuity without creating a centrally readable archive.
Messages and files behave differently
The system keeps offline messaging useful without turning file storage into a cloud locker.
Direct file bytes
File data transfers peer to peer and is not stored for offline retrieval. A pending transfer resumes after both devices are online again.
Voice and video
WebRTC negotiates live media between call participants. Network conditions determine whether the path is direct or needs relay assistance.
Multiple devices
A QR handoff authorizes another browser and transfers encrypted account state. Drafts and messages synchronize as authorized devices reconnect.
What “mini-node” means in QEYET
A mini-node is a participating client or community node that contributes bounded routing and encrypted-envelope storage. Federation peers provide stable rendezvous and availability while browser mini-nodes add capacity when they are online. This is a cooperative mesh, not a promise that every browser can replace internet-addressable infrastructure.
Resilient, not magically infrastructure-free
At scale, user participation reduces pressure on stable peers. Public rendezvous, push delivery, abuse controls, and difficult NAT paths still require reachable infrastructure and operational monitoring.