Jami vs Threema

What Jami is

Jami is a free/libre GNU communication application licensed under GPLv3-or-later. It offers end-to-end encrypted instant and group messaging, audio/video calls, conferences, screen sharing, file transfer and SIP-client capability on Linux, Android, Android TV, Windows, macOS and iOS. User media and messages are designed to flow peer to peer rather than through a hosted relay. That does not mean every deployment has zero infrastructure: public operation normally uses DHT bootstrap and name services, TURN may relay connectivity when direct paths fail, and mobile clients may use a DHT proxy plus platform push services. Organizations can self-host these pieces and use the separate JAMS server for LDAP, Active Directory or local-account enrollment.

What Threema is

Threema is a Swiss secure-messaging family rather than one subscription. Threema Private is a consumer mobile app that can be purchased directly for Android for a current one-time price of $7.49, €6.49 or CHF 5.99 and can create an identity without supplying a phone number or email. Threema Work adds annual per-user licensing, a management cockpit, app configuration, optional Broadcast and Gateway components, and a 30-day trial for up to 30 users. Threema Gateway is a separate credit-based API integration. Apps are open source and communications use end-to-end plus transport encryption, but server code and the operating environment are separate trust and audit scopes.

What Jami is built to do

Peer-to-peer communication

Routes encrypted messages, calls and files directly when network conditions allow.

Calls and conferences

Provides audio/video calling, group conferencing, Rendezvous points and screen sharing.

Multi-platform clients

Runs on Linux, Windows, macOS, Android, Android TV and iOS with differing feature support.

Enterprise JAMS

Optionally enrolls users through LDAP, Active Directory or an embedded database.

What Threema is built to do

Private messenger

Provides identity-minimizing encrypted chat, voice/video calls and file exchange for consumers.

Threema Work

Adds managed users, configuration, MDM compatibility and enterprise administration.

Broadcast

Supports separately entitled one-to-many communication workflows.

Gateway API

Connects business software through credit-based server-encrypted or client-side E2E modes.

Choose Jami if

• Open-source communities wanting chat, calling and files without a SaaS seat fee
• Local-network or sovereign deployments prepared to run bootstrap, TURN and naming components
• Enterprises willing to operate JAMS for directory-backed enrollment

Skip Jami if

• A vendor-operated workspace with turnkey compliance retention and administrator reporting is required
• The team cannot troubleshoot NAT, TURN, push delivery, certificates or multi-device synchronization
• Feature parity across every desktop, Android, Android TV, iOS and web client is assumed without testing

Choose Threema if

• Individuals wanting a paid messenger without mandatory phone-number identity
• Organizations centrally configuring encrypted mobile communication through Threema Work
• Systems sending transactional Threema messages through a deliberately selected Gateway encryption mode

Skip Threema if

• A free consumer messenger with a large existing contact network is the priority
• Enterprise selection is based on the consumer one-time price
• Identity lifecycle, device backup, administrator visibility, Gateway keys and annual renewal have not been tested

Jami: pros & cons

• Free GPL-licensed clients cover major desktop and mobile platforms without advertising or feature-plan limits.
• Messaging, calls, conferencing, files and screen sharing are E2EE and normally peer to peer.
• Local-network communication and configurable bootstrap, TURN, proxy and name services support autonomous deployments.
• JAMS can add enterprise enrollment and LDAP or Active Directory-backed credentials without replacing distributed communication.
• Direct peer connectivity depends on reachability; NAT traversal can require a TURN relay and therefore additional infrastructure and bandwidth.
• Default bootstrap, name, DHT-proxy and mobile push services qualify simplistic claims that Jami needs no servers at all.
• iOS background operation effectively requires push notification infrastructure; only some surrounding services can be self-hosted.
• JAMS introduces certificate authority, directory, server-hardening, backup and lifecycle responsibilities and is not the same as consumer Jami being centrally managed by default.

Threema: pros & cons

• Messages, calls and files use end-to-end encryption with keys tied to a randomly generated Threema ID.
• Consumer identity can be created without making a phone number or email mandatory.
• Open-source apps and published security material provide inspectable implementation evidence.
• Threema Work adds centralized configuration and deployment, while Gateway supports programmatic messages.
• Private, Work, Broadcast, Gateway and OnPrem have different licensing, administration and deployment boundaries.
• The $7.49 figure is a direct Android consumer license, not a Threema Work enterprise seat or iOS universal price.
• Work contracts are annual, prepaid and auto-renew unless cancelled at least 90 days before term end.
• Gateway Basic mode lets the server handle encryption and private keys; true E2E mode requires correct client-side key operations.