VeraCrypt vs Matrix

Veracrypt is an on-the-fly encryption tool. Meaning that it decrypts files only when they are needed and that the files are otherwise kept encrypted the rest of the time.

This project is free and users are encouraged to donate something to keep the project going.

Supports AES, TwoFish and Serpent encryption cyphers.

The source code is open to review. It has already had a security audit and it did well, with small problems fixed by authors within days of being reported. Its predecessor source, Truecrypt, had a detailed audit that found its capabilities sound, completed (ironically) shortly before the TC folks decided to call it quits. Anyone skeptical or curious about what it does can see how it works, at the gut level.

Most Intel and AMD (and possibly other) CPUs have AES specific instruction sets, so you needn't task the CPU during the en/de/crypt process when using AES, VC throughput is as if the code were in 'firmware'; you can see the effect if you choose anything but AES as your cipher.

It can create containers (like a encrypted folder) which is very useful.

Veracrypt is in active development with constant and regular updates and several external audits in the planning stages.

Veracrypt is supported on MacOS, Linux and Windows.

It's easy to understand and use.

Matrix is an open standard, defining simple HTTP APIs so that devs can easily write their own clients, bots, bridges or servers. You're not locked into a specific set of implementations.

Matrix has bridges to IRC (freenode, moznet, oftc, snoonet etc), Slack, Gitter, Rocket.Chat, XMPP, SMS, SIP and others. The point is to 'matrix' all the different networks out there into one single decentralised network.

Riot.im is the easiest way to use Matrix, with great clients for Web, iOS and Android (and Fdroid).

Matrix is decentralized, there's no one central point that the information goes through and so no once central point of failure or control.

Matrix aims to "provide an analogous ecosystem to email - one where you can communicate with pretty much anyone, without caring what app or server they are using" using a neutral identity system.

Matrix is designed to support Instant Messaging, VoIP/WebRTC signalling (voice and video) and Internet of Things communication.

Riot.im includes an app store with integrations for Github, JIRA, Jenkins, Giphy etc - and anyone can add more via Matrix.

Which can be found here.

Matrix is designed to support Instant Messaging, VoIP/WebRTC signalling and Internet of Things communication and allows cross-communication between those services. Meaning one person could be using IRC and another Slack for IMs, or one person could be using Skype and another Google Hangouts for videoconferencing.

Matrix features end-to-end encrypted chats which are syncronized accross all your devices.

E2E is implemented in the matrix-js-sdk library and Riot.im client.