Keys stay with devices
Messages are encrypted before entering the network and opened only by authorized recipient devices.
Private communication, without an identity tax
QEYET
Encrypted chats, calls, files, groups, and private AI sessions with keys controlled by your devices.
- No phone number
- Local message history
- Six-word recovery
Built differently
Your conversations are not a company database.
QEYET combines device-controlled identities, encrypted delivery, direct peer connections, and community-run mini-nodes. The result is a messenger designed around user custody instead of content collection.
Mini-nodes carry ciphertext
Available nodes help encrypted envelopes reach offline contacts without receiving conversation keys.
History remains local
Message history and cached media stay on your devices unless you deliberately export an encrypted backup.
One private workspace
The communication tools people already expect.
QEYET keeps the familiar parts of modern messaging while changing who controls the underlying data.
Messages and groups
Direct chat, group conversations, replies, reactions, edits, delivery states, folders, drafts, and disappearing messages.
Voice and video
Encrypted WebRTC calls with direct connections when network conditions allow and relay fallback when they do not.
Direct file transfer
Files move device to device, expose transfer status, and resume when both participants reconnect.
Multiple devices
Authorize another browser with a QR code and synchronize encrypted account state among your own devices.
Enterprise spaces
Tenant-managed access, private company directories, spaces, scheduled meetings, and administrative recovery controls.
Hermes sessions
Connect a user-owned Hermes Agent and keep separate sessions, workspace memory, rich text, tables, and charts in QEYET.
Security without fog
Clear claims. Clear limits.
QEYET uses Olm Double Ratchet sessions through Matrix Rust SDK Crypto, signed device identities, encrypted local vaults, and WebRTC media protection. Routing infrastructure can still observe network metadata such as timing, addresses, and approximate encrypted packet size.
QEYET does not claim to be the Signal Protocol, and the complete QEYET product has not yet completed an independent security audit.
Read the security architecture- Message sessions
- Olm Double Ratchet
- Local vault
- AES-256-GCM
- Recovery derivation
- PBKDF2-SHA-256
- Calls
- WebRTC encryption
QEYET Enterprise
Company control without a company-readable message archive.
Organizations can govern membership, directories, spaces, meeting access, and account reissuance while message content remains encrypted for authorized participant devices.
Explore enterpriseStraight answers
Common questions
Does QEYET require a phone number?
No. A standard identity is created in the browser and protected by six recovery words.
Are offline messages possible?
Yes. Encrypted message envelopes can wait in the sender outbox or on available mini-nodes. File bytes transfer directly and therefore wait until both users are online.
Can QEYET read messages?
QEYET routing nodes carry encrypted envelopes and do not receive conversation keys. Authorized participant devices decrypt message content.
Where is message history stored?
History is stored locally on authorized devices. Deleting local data removes that device's history; recovery words restore identity, not deleted messages.