Jami Concepts

Jami is a quite complex platform interacting with many different components and introducing many new concepts. This manual is intended to help you understand how Jami works, how to develop for Jami, and how to contribute to the project.

To quickly summarize and help you to find the part of the manual that you are looking for, here is a brief overview of the different sections:

Jami is a distributed platform that allows users to communicate without the need for a central server. So, a Jami account consists on a chain of certificate (CA, Account, Device) that is used to authenticate the user and to encrypt the communication. The account is stored on the user’s device, not on a server.

For this, here is the page that explains how it works: + account-management + jami-identifiers

After the user account is created, the user can contact other people by sending connection requests through a DHT (https://opendht.net) after finding the contact id (directly known or by lookup the name server). If both parties agree, they will first try to create a p2p TCP link (with the ICE protocol), then encrypt it via TLS and use it as a multiplexed socket to transmit data for various protocols c.f.:

  • contact-management

  • banned-contacts

  • connection-manager

  • name-server-protocol

When both peers are in their contact list, a conversation is created. This conversation is called a Swarm. A swarm is synced between all devices in a conversation via the git protocol (it’s a git repository) and connections across devices in a conversation are routed by a component called the drt (distributed routing table).

  • swarm

  • drt

Then, the connection can be used to send messages, files, or to make calls (1:1 or conferences).

  • calls

  • calls-in-swarm

  • file-transfer

  • conference-protocol


Calls may be fully replaced by call in swarms in the future (except for SIP accounts)

Finally, a user can have multiple devices and a lot of information is synced between them.

  • synchronizing-profiles

  • synchronization-protocol