Compared with WhatsApp and Signal

All three encrypt messages end to end on the Double Ratchet principle. Signal remains the reference for confidentiality, metadata frugality, openness and independent review. WhatsApp uses the same messaging protocol but is closed as an app and collects extensive metadata. TalX stands out through serverlessness in three stages, through doing without a phone number and an account, and through a hybrid post-quantum share right in the ratchet root key.

Operation and identity

Criterion	TalX	WhatsApp	Signal
Operating model	serverless / P2P; internet delivery through project-run brokering, self-hostable at any time	centralised at Meta	centralised at a non-profit foundation
Account / registration	no account, no phone number; a self-generated key pair	phone number and corporate ecosystem mandatory	phone number mandatory
Platforms	Android only (8 and newer)	Android, iOS, desktop, web	Android, iOS, desktop
Openness	source-available, no reproducible builds	app closed	fully open source, reproducible builds
Independent external audit	no – internal reviews only	protocol audited, app not inspectable	yes, several times

Encryption

Criterion	TalX	WhatsApp	Signal
End-to-end encryption	Double Ratchet	Signal protocol	Signal protocol
Handshake	X3DH-lite with rotating prekeys, serverless	X3DH with a prekey server	X3DH, now PQXDH, with a prekey server
Post-quantum protection	hybrid ML-KEM-1024 in the ratchet root key	no PQ publicly known	PQXDH in the handshake, PQ ratchet rolling out
Forward secrecy from the 1st message	yes, without a prekey server	yes	yes
Groups	sender keys with rotation, distributed serverlessly	sender keys, distributed server-side	sender keys plus anonymous group credentials
Data on the device	SQLCipher, attachments AES-GCM, master secret hardware-wrapped	in-app, backup optionally end-to-end	encrypted in-app
Backup protection	Argon2id (64 MB / 4 passes) + AES-GCM + mandatory second factor	password or a 64-character key, optional	local; secure cloud backups rolling out
Pairing and verification	QR, NFC, J-PAKE code; safety number, warning on key change	QR safety number	QR safety number, key transparency

Delivery

Criterion	TalX	WhatsApp	Signal
Offline over Bluetooth, no internet	yes	no	no
Direct connection on a local network	yes – delivery in seconds with no server at all	no	no
Calls without a server on the same Wi-Fi	yes – voice and video	no	no
Delivery while the app is closed	yes – brokering plus a push wake-up	yes, worldwide	yes
Transport path visible per message	yes	no	no
Metadata at the operator	offline and on a LAN: none. Over the internet: who, with whom, when	extensive, linked across the group	minimal (sealed sender, private contact discovery)

Feature set

Criterion	TalX	WhatsApp	Signal
Interface languages	91, fully translated	very many	very many
Transcription of voice messages	yes – on the device, 6 languages, configurable per chat	yes – processed server-side	no
Translation of messages	yes – on the device, 20 languages	yes – via cloud services	no
Delete for everyone / edit	yes / yes (text, up to 5 minutes)	yes / yes	yes / no
Block contacts	yes – survives a re-pairing	yes	yes
“View once” media	yes – disappears on the sender’s side too	yes	yes
Disappearing messages with a timer	no	yes	yes
Attachments	up to 100 MB (groups 50 MB)	up to 2 GB	up to 100 MB
Very large groups	no	yes	yes
Group calls	no	yes	yes

Where each app leads

TalX

Three stages of serverlessness: Bluetooth radio, a direct connection on the local network, internet P2P – including voice and video calls with no server at all on the same Wi-Fi.
No phone number, no account. Brokering and push out of the box, both self-hostable.
A post-quantum share right in the ratchet root key.
Transcription and translation on the device – features that elsewhere hand content to the cloud.
Forward secrecy from the first message without a prekey server; a self-healing session.
Pairing via J-PAKE, remotely too with a short code.
Backup with Argon2id and a mandatory second factor.
The transport path actually used is shown on every single message.

Signal

Independently audited, fully open source, reproducible builds.
Exemplary metadata frugality: sealed sender, private contact discovery, private groups.
A mature handshake, PQ ratchet rolling out, a codebase proven over years.
All platforms; a non-profit operator with no advertising incentive.

Ubiquitous – almost every contact is reachable.
Very robust, low-latency delivery and calls worldwide, on all platforms.
A solid encryption basis despite the closed app; very large groups and very large attachments.

Recommendation by use case

Use	Recommendation
Highest confidentiality, highly sensitive	Signal – independently audited, mature, metadata-frugal
Communication without internet or without a phone number	TalX – works offline over Bluetooth, no account
Home or office on the same Wi-Fi, calls included	TalX – no server at all, in seconds
Transcribing voice messages without giving content away	TalX – runs on the device
Maximum everyday reachability	WhatsApp – network effect, metadata accepted deliberately
Data sovereignty, self-hosting, tinkering	TalX – full control, but still without an external audit
A mixed device world with iOS or desktop	Signal or WhatsApp – TalX is Android-only
Very large groups, very large files	WhatsApp – TalX is deliberately limited here

The chapter that belongs with this

A comparison that lists only your own strengths is advertising. The full list of the points where TalX falls behind therefore has a page of its own: limits, stated openly.