Secure video chat via pure WebRTC
Welcome to Briefing. Yet another secure video chat.
Privacy is the driving force behind this project. It uses secure technologies like WebRTC to directly connect between participants. The website that provides the web app and mediates the communication stores as few data as possible and does not know anything about the contents of established conversations. No accounts are required. No cookies are used.
The difference between Briefing and most similar projects is, that it does not use a central server that distributes the video streams (SFU). The advantage of an SFU is that it saves bandwidth due to the fact that the own video does not being uploaded to each participant but only once. The SFU can also do more optimizations the clients might not support. But then the video signal is not end-to-end encrypted any more i.e. you have to trust the SFU provider. Briefing instead sends data from peer to peer directly ("Mesh") and therefore the data does not travel over the server under normal operation. The WebRTC peers however still trust the signaling server for the authenticity of the peer-to-peer communications encryption in place.
FAQ- Some answers to some questions
Why starting another video conf tool?
During the Corona pandemic I tried to create a peer-to-peer solution for home schooling called peer.school. Although the project has been retired for various reasons, I learned so much about WebRTC and video/audio communication, that I did want to reuse this knowledge in this project.
Why is it free and Open Source?
Only a free project does not require the user to create an account and unveil payment information, that could be used to identify that person. This is why the project is free and will remain free, as long as no additional costs like maintaining TURN servers etc. will require some funding. If you want to support me and the project directly you can via Github or via PayPal. If you are interested in sponsoring please contact me at [email protected].
Which servers are actually involved in a call?
- Briefing web site (provides the web app)
- Briefing signaling server (coordinates peers in rooms)
- Briefing STUN/TURN server (helps traversing fire walls)
Feature X is missing! Found bug Y!
Please visit the GitHub project to see if your request is already on the list or place a new issue. Your contribution is of course welcome as well.
How about native apps?
Frankly this is not required, because your browser can handle it all. You can of course put Briefing on your home screen e.g. in iOS Safari tap on the "Share" icon and choose "Add to Home Screen". You can do the same in browsers like Google Chrome.
License
Briefing is free and can be modified and forked. But the conditions of the EUPL (European Union Public License 1.2) need to be respected, which are similar to ones of the GPL. In particular modifications need to be free as well and made available to the public.
For commercial use please contact [email protected] for licensing alternatives.
Get a quick overview of the license at Choose an open source license. This license is available in the languages of the European Community.
Author
My name is Dirk Holtwick. I'm an independent software developer located in Germany. Learn more at hotlwick.de.
Fund this project by sponsoring via GitHub.