PRIVATE BY DESIGN. CONNECTED BY YOU.

A closer connection.
A quieter kind of chat.

Private messaging, thoughtfully designed. Share text, voice messages, photos and files through a server you choose — with a familiar, beautifully simple experience.

A fresh blue identity · In developmentNative on three platforms · Your cloud or local network

Illustrative product preview · Sample conversation
End-to-end encryptedOlm / Megolm
✓
Your connection. Your choice.↗
Illustrative product preview · Sample conversation
Three native clientsMatrix encryptionLAN or cloud hostingMessage retention controls

Communication, made familiar

An everyday messenger.
A considered approach to privacy.

No new way of chatting to learn. Keep the complexity in the encryption, and the conversation where it belongs.

01 / 03

Even a simple hello deserves protection.

Clear conversations and familiar message bubbles. Share text, photos, voice messages and files in one natural flow.

Illustrative interface previews. Each platform uses native controls; final screens may differ in the approved test release.

Daily conversations
Daily conversations
LIANCHAT / NATIVE EXPERIENCE

Security starts at the endpoints

Carry the message.
Protect the conversation.

Built on Matrix end-to-end encryption. Messages and attachments encrypt and decrypt on the clients, while the server carries ciphertext.

01

Text and attachments, protected together

Text, photos, voice messages and files all take part in encrypted one-to-one conversations.

02

Privacy controls you can see

Encryption status and retention settings sit inside the conversation, with important choices close at hand.

Your device
Encrypted in transit
7f a2 9c e4 01c8 3d f1 62 b041 ee 9b 70 a8
Their device

Encryption and decryption happen on the clients

Olm / MegolmHTTPS / TLSMatrix

Device identity verification is still in development. Encryption does not hide all communication metadata. Use test content in this preview.

Infrastructure on your terms

Your server.
Your space to communicate.

One client, different deployments. Run the backend on your LAN or in your own cloud, and choose where your communication infrastructure lives.

Connect across the distance.

A trusted HTTPS endpoint connects your cloud deployment to test devices in different locations.

Self-hosted serverHTTPS

One client. Your server address.

A lighter starting point for a small deployment.

A single-node architecture and bounded caches reduce always-on components. Test deployment completed on a 1 vCPU, 2GB cloud server.

This deployment is not a concurrent-user capacity claim.
1vCPU2GBRAM
Official test server APIhttps://im.lianchat.app

Open LianChat → Select communication server → Enter API address

Retention period 24hLocal timer after viewing 30s
L

See you Saturday. Let me know when you arrive.

09:41 ✓✓
↻
After viewing, the local message follows your timer

Local-timer concept · accelerated illustration

Conversations have their own rhythm

A moment, on your terms.

Choose how long new messages stay on the local timeline. Keep local visibility, explicit exports and server retention policies distinct.

Local clearing does not erase copies on the peer, server or exported files. Cross-device timers and per-message remote destruction are still in development.

MADE FOR YOUR EVERYDAY

One LianChat.
Made for your devices.

Native apps for iOS, Android ARM64 and HarmonyOS are being brought together. Downloads will open after the release is approved.

Android ARM64

ARM64 only. A native experience, designed around everyday conversations.

Native appRelease in review

iOS

A native iOS experience. Available after test devices and signing are confirmed.

Native appRelease in review

HarmonyOS

A native HarmonyOS app, with platform features under joint validation.

Native appRelease in review

Downloads are not open yet. No installer is linked on this page. Approved builds and supported signing options will be published here after release review.

Encrypted text and multimedia direct messaging are available in development testing. Account deletion, encrypted live calls and iOS background calling remain under implementation and validation.

A few things before you begin

Can one client connect to different servers?+

Yes. The welcome screen keeps a manual server API address setting. Use the same client with different cloud or LAN deployments, without rebuilding it for each server.

What can I share today?+

The current preview supports end-to-end encrypted text, photos, voice messages and files in one-to-one chats, with a 20MB attachment limit. Live calls and platform push are in development.

Does local clearing erase every copy?+

No. Current timers affect the local timeline and its previews. They do not guarantee erasure on peer devices, servers, runtime copies, system backups or exported files. Cross-device timers and per-message remote destruction are not implemented yet.

How do I get started?+

Downloads will open after release approval. Install the build supported by your platform and signing profile, then enter your server on the welcome screen. A bare host such as im.lianchat.app defaults to HTTPS. Registration uses an account name, an SMS code and password confirmation.

Make every connection
your own.

Explore the apps ↗