For the record, we built a similar offering, cf. https://github.com/wallix/datapeps-sdk-js https://github.com/wallix/datapeps-sdk-js (in my previous life). We

For the record, we built a similar offering, cf. https://github.com/wallix/datapeps-sdk-js https://github.com/wallix/datapeps-sdk-js (in my previous life). We started the implementation after the Snowden revelations, tied to a web messaging platform called PEPS but after the sale of the company we realized that most of the value lied in the E2EE SDK itself, and not the messaging app. We got there as many prospects were interested in the encryption part, but did not want yet another messaging platform. I am still unsure about the market for this (disclaimer: I am no longer at Wallix, so I am not involved anymore with DataPeps although I created it). It was a tough sale, even as a part of an existing company with hundreds of customers. Many people felt the need for privacy, but were not ready to implement a new product or to involve developers to modify an existing product. I do feel though that there is a need for a truly, non-profit, open source solution that handles E2EE. It would be highly beneficial for the whole developer ecosystem. The DataPeps SDK (MIT license) is a good start. The accompanying service is currently proprietary.