SimpleX Chat vs Tawk.to

SimpleX Chat is deep in a v7.0 beta cycle, six betas in, with the stable armv7a tag now cut. The release is dominated by channels: broadcast surfaces with subscribers, contributor and moderator roles, searchable subscriber lists, and CLI access. Alongside them sits SimpleX names — registerable, resolvable names for channels and businesses — and per-server role controls that let self-hosters run a relay that handles only message reception, private routing, or name resolution.

This is the hardest problem the project has taken on. SimpleX's premise is that users have no identifiers at all, and public channels need exactly the opposite: a stable name people can find and an author they can verify. The answer taking shape is cryptographic rather than account-based — message signing, member security-code verification, and name resolution run as an opt-in server function. The betas since then have shifted from adding channel features to hardening the role model, rejecting forwards from unexpected admins and locking relay-role assignment.

A 7.0 stable release looks imminent given the non-beta tag, with message signing held back for 7.1 as the notes state. Expect the next cycle to turn signing on and continue tightening who can act as a relay or admin inside a channel.