Answering means staying connected.
A cross-region accept now closes only other still-ringing devices. The phone or browser that answered never receives the answered-elsewhere event as a hangup.
USA ↔ Iran · stale-device safe · no instant teardownLIVARA 0.9.16 / WEB + ANDROID / 2026
Say it likenobody elseis listening.
Livara is a private, end-to-end encrypted messenger for web and Android.
Livara is a fast messenger with a deliberately clear boundary: LVR1 seals direct-message text and media; LGS1 seals compatible private-group text and media-key messages. Android adds 2–6-person audio/video rooms and screen sharing. Channels, group membership, reactions and some control metadata remain outside the E2EE claim. The custom protocols are not independently audited.
Free to use0.9.16 current release0 quiet downgrades
sealed on your deviceouter field
relay sees ciphertext
Direct messages are end-to-end encrypted◆Compatible private-group text and media are end-to-end encrypted◆Android group audio, video and screen sharing support 2–6 people◆Channels and some control metadata are not◆Verify the build before installing◆Direct messages are end-to-end encrypted
Privacy you can point at
The line is right here.
“Encrypted” is not a useful answer until you know what, where, and from whom. This is the complete boundary—not the flattering half.
Sealed end to end
closed on your device, opened only on theirs
- Direct message text, and every edit to it
- Photos, video and files — encrypted before upload
- Captions and filenames, not just the bytes
- Voice notes and round video messages
- Private-group text and media keys (LGS1)
- Pairwise-sealed setup for direct and Android group calls
Visible to the server
disclosed, not hidden — the trade you are actually making
- Who talks to whom
- Group membership, which the server still controls
- Timestamps, ciphertext sizes and delivery state
- Reactions and some control relationships
- Channels — a publication surface, readable by design
- LSS1, the metadata-protection work, exists in the codebase but is not wired into ordinary sending yet. When it is, this column gets shorter — and this page will say so on the day, not before.
01:01
A small table with a very large job.
Compatible direct and private-group content closes before upload. The table keeps channels and routing metadata separate, and the threat model separately records that LGS1 membership is supplied by the server.
See the full threat model ↗| What it is | Direct 1:1 | Groups | Channels |
|---|---|---|---|
| Message text | Sealed on your device | LGS1 sender-key sealed | Server can read it |
| Text edits | Sealed on your device | LGS1 sender-key sealed | Server can read them |
| Photos, video, files, captions | Encrypted before upload | Encrypted before upload | Server can read them |
| Who you talked to | Server knows | Server knows | Server knows |
| When you talked | Server knows | Server knows | Server knows |
| Your password | Never leaves your device | Never leaves your device | Never leaves your device |
| Your private keys | Never leave your device | Never leave your device | Never leave your device |
Engineered like infrastructure
Six things worth arguing about.
Every messenger has a message box. These are the six decisions underneath one — including the two that cost us something to admit.
Encryption that refuses to degrade
LVR1 mixes P-256 with ML-KEM-768, advances a one-way chain before every send, and seals content with AES-256-GCM. If it cannot seal a protected message, it refuses to send it — there is no quiet fallback to plaintext.
Read the protocolGroups with the asterisk printed large
LGS1 gives every sender their own signed chain, so one ciphertext reaches the whole group. Honest membership changes force fresh keys. The server still supplies the member list, and that gap is documented rather than decorated.
See the limitBuilt for the tunnel, not the demo
Sends made offline are staged, sealed and queued under one stable operation ID. On reconnect the client asks for the exact range of sequence numbers it missed and applies it once. Bad signal is a designed-for case, not an apology.
Watch it recoverAn assistant that stays on the handset
Livara AI drafts, rewrites, summarises and proposes actions using a model running on your Android device. Nothing is saved until you confirm it. Livara AI Pro is separate, opt-in, admin-granted and explicit about where the text goes.
Meet Livara AIA call room that can share the screen
Direct voice/video plus 2–6-person Android group rooms use DTLS-SRTP peer links and pairwise-sealed signaling. Screen sharing, reconnect recovery and adaptive quality ship now; MLS/SFrame and post-quantum call media do not.
See what shipsA lab instead of an adjective
Anyone can print “military-grade” on a page. Hash the APK in your own browser, run real P-256, HKDF and AES-GCM, corrupt a ciphertext and watch authentication reject it. Count the uploads while you do it: zero.
Run the Proof LabStable calls and smaller delivery
The update changes real boundaries.
This release fixes immediate hangups, duplicate encrypted accepts and dropped call-control events across both regions, then delivers build 114 to build 113 as a verified incremental patch.
Encrypted accepts are idempotent.
Duplicate accept frames are ignored while the first answer opens, and LCS2 keeps a signed compatibility copy until both clients prove the secure session is ready.
replay-safe · web/Android parity · fail-closed authThe fix stays a small update.
Build 113 installs 114 from a signed 113→114 delta. Livara reconstructs the complete APK locally, verifies every byte and signer, and can switch regional release servers without weakening verification.
signed delta · exact reconstruction · Iran/USA fallbackLivara AI
An assistant in your pocket, not in a data centre.
Draft the difficult message. Continue the thought. Summarise yesterday’s two hundred unread. Turn “coffee tuesday, 5pm” into a proposed reminder you review before anything is saved. The model runs on the Android device, so the conversation it reads never becomes someone else’s training corpus.
Need more than the handset can carry? Livara AI Pro is opt-in, granted per account by an administrator, permissioned per chat, and explicit about its path — device, then Livara, then Google. No silent cloud copy, no hidden AI history.
on-device by default the session stays open English & فارسی
How the assistant behavesProof Lab
Check the build
yourself.
Five instruments that run entirely in this browser tab. They are here because “military-grade” is a word anyone can type, and a checksum is not.
Open the Proof Lab ↗- SHA-256
- Hash the Android build in this tab and compare it with the digest published on this site.
- AES-256-GCM
- Seal a message, open it again, then change one byte and watch authentication refuse it.
- P-256
- Generate a real key pair using the browser's own crypto engine, not a picture of one.
- Fingerprints
- Produce two identities side by side and check that no two of them read alike.
- Network
- There is no upload endpoint on this page. Disconnect and every instrument still runs.
Web when you want it. Native when you need it.Pick up where
Pick up where
you left off.
Start in a browser, continue on Android, disappear into a tunnel, and come back to one timeline. The Android app keeps an encrypted local cache and a retrying outbox built for bad connections.
Nadia R.SEALED · LVR1 HYBRID-PQ
did the checksum match?21:04
yeah. same 64 characters, byte for byte.21:04
8F2A C40E 91BD 77A3 E5F0 1C98 B6D2 4A71 0E33 A8C5WHAT THE RELAY STORED
so the server just moved that?21:05
that is the whole job. it never had the key.21:05
Message
256bit AES-GCM keys, one per message
768ML-KEM parameter set in the hybrid root
0phone numbers, ads or trackers required
5checks you can run yourself, offline
Written by the people building it
Read what private messaging looks like from the inside.
Guides, product decisions, uncomfortable trade-offs, and plain-English security notes — in English and Persian.
- Security noteswhat changed in the protocol, and what it costs you
- Product decisionsincluding the ones that did not go our way
- Useful guidesset-up, recovery, and verifying a build
Your people are waiting.
Sealed, and in sync.
Free. No phone number. No advertising, and no processing of message content for it. Read the limits first if you would rather — they are on the same site, in the same font, at the same size.