Communication between independent parties

Several independent parties want to communicate with each other, e.g.:

  • Aid agencies in a crisis situation
  • A congress with different parties

When different parties (aid agencies, organisations) work together, there is also communication. This communication can take place via various media and should serve to provide support.

However, since various parties are involved, it must not be the case that one party is overprivileged, i.e. having access to third party data.

In addition, the system should be quickly deployed and quickly dismantled after use. After dismantling, all parties should have the same rights to the stored data.

Functional requirements for the system


Group Messaging

Drawing Board

Conference Calling


Each party already communicates via its own system
The parties do not trust that the respective systems are secure.
There is no common platform that distributes data sovereignty among all parties.
If a party were to provide its own system, that party would be responsible for the entire data management
Each party has the same rights to the data

Possible solutions

Use a cloud solution, such as Microsoft Teams, and have a third-party provider run it

Each party must trust this cloud provider

Identity management and operation is necessary

Third party vendors and operators have access to data

Setting up the system takes a lot of time

A third-party vendor builds a system on-premises, such as Skype

Central systems require high infrastructure expenditure for operation

Identity management and operation necessary

Third party vendors and operators have access to data

Setting up the system takes a lot of time

Set up a decentralized system in which the data belongs exclusively to the user. The system has a decentralized identity management and can be used on any device.

Solution with kaila

A possible solution can be the development of an application based on kaila. All common requirements of centralized systems can be fulfilled, but also the privacy of the users is guaranteed.

  • kaila can be operated in a cloud infrastructure without any problems, as all data is encrypted, making it impossible for the cloud provider to view the data.
  • kaila can also be deployed spontaneously at any location within a very short period of time, because the requirements for the infrastructure are very low.
  • kaila could also be operated by several parties with a federation put in place

kaila needs the following infrastructure components

  • MQTT broker (with SMOKER extension)
  • Stun/Turn Server, if there are network transitions
  • Web server for the application (the application could also be distributed beforehand)

In order to optimize our website for you and to continuously improve it, we use cookies. By continuing to use the website, you consent to the use of cookies. For more information on cookies, please refer to our Privacy Policy.