You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
jfinn e49302bfe6 auto acp scripted 4 lat temu
.github what have I done? 5 lat temu
android what have I done? 5 lat temu
connection_optimization what have I done? 5 lat temu
css what have I done? 5 lat temu
debian what have I done? 5 lat temu
doc what have I done? 5 lat temu
flow-typed/npm what have I done? 5 lat temu
fonts what have I done? 5 lat temu
images what have I done? 5 lat temu
ios what have I done? 5 lat temu
lang what have I done? 5 lat temu
modules auto acp scripted 5 lat temu
rdev auto acp scripted 5 lat temu
react auto acp scripted 5 lat temu
resources what have I done? 5 lat temu
rldjs auto acp scripted 5 lat temu
service what have I done? 5 lat temu
sounds what have I done? 5 lat temu
static what have I done? 5 lat temu
.buckconfig what have I done? 5 lat temu
.editorconfig what have I done? 5 lat temu
.eslintignore what have I done? 5 lat temu
.eslintrc.js what have I done? 5 lat temu
.flowconfig what have I done? 5 lat temu
.gitattributes what have I done? 5 lat temu
.gitignore what have I done? 5 lat temu
.travis.yml what have I done? 5 lat temu
.watchmanconfig what have I done? 5 lat temu
CONTRIBUTING.md what have I done? 5 lat temu
ConferenceEvents.js what have I done? 5 lat temu
LICENSE what have I done? 5 lat temu
Makefile auto acp scripted 4 lat temu
README.md what have I done? 5 lat temu
analytics-ga.js what have I done? 5 lat temu
app.js what have I done? 5 lat temu
base.html what have I done? 5 lat temu
body.html what have I done? 5 lat temu
conference.js what have I done? 5 lat temu
config.js what have I done? 5 lat temu
connection.js what have I done? 5 lat temu
favicon.ico what have I done? 5 lat temu
fqdn_conf.js auto acp scripted 5 lat temu
fqdn_conf_i0.js auto acp scripted 5 lat temu
head.html what have I done? 5 lat temu
i0.html what have I done? 5 lat temu
i0_conf.js auto acp scripted 5 lat temu
i1.html what have I done? 5 lat temu
i1_bak.html what have I done? 5 lat temu
i2.html what have I done? 5 lat temu
i3.html what have I done? 5 lat temu
i4.html what have I done? 5 lat temu
i5.html what have I done? 5 lat temu
i6.html auto acp scripted 5 lat temu
i6_v2.html auto acp scripted 5 lat temu
i6_v3.html auto acp scripted 4 lat temu
i7.html what have I done? 5 lat temu
i8.html auto acp scripted 5 lat temu
i8_v2.html auto acp scripted 5 lat temu
i9.html auto acp scripted 5 lat temu
i10.html auto acp scripted 5 lat temu
iconf.js auto acp scripted 5 lat temu
index.android.js what have I done? 5 lat temu
index.html what have I done? 5 lat temu
index.ios.js what have I done? 5 lat temu
index_bak2.html what have I done? 5 lat temu
index_dev.html what have I done? 5 lat temu
index_old.html what have I done? 5 lat temu
index_orig.html what have I done? 5 lat temu
index_orig_fix.html what have I done? 5 lat temu
inline_script.js what have I done? 5 lat temu
inline_script_eapi_mod.js auto acp scripted 5 lat temu
interface_config.js what have I done? 5 lat temu
interface_config_dev.js what have I done? 5 lat temu
logging_config.js what have I done? 5 lat temu
meet.jit.si_fqdn_conf.bak.js auto acp scripted 5 lat temu
meet.jit.si_fqdn_conf.js auto acp scripted 5 lat temu
meet.jit.si_iconf.js auto acp scripted 5 lat temu
metro.config.js what have I done? 5 lat temu
package-lock.json what have I done? 5 lat temu
package.json what have I done? 5 lat temu
plugin.head.html what have I done? 5 lat temu
redir_index.html what have I done? 5 lat temu
rldjs.js what have I done? 5 lat temu
t0.html what have I done? 5 lat temu
title.html what have I done? 5 lat temu
webpack.config.js what have I done? 5 lat temu

README.md

Jitsi Meet - Secure, Simple and Scalable Video Conferences

Jitsi Meet is an open-source (Apache) WebRTC JavaScript application that uses Jitsi Videobridge to provide high quality, secure and scalable video conferences. Jitsi Meet in action can be seen at here at the session #482 of the VoIP Users Conference.

The Jitsi Meet client runs in your browser, without installing anything else on your computer. You can try it out at https://meet.jit.si.

Jitsi Meet allows very efficient collaboration. Users can stream their desktop or only some windows. It also supports shared document editing with Etherpad.

Installation

On the client side, no installation is necessary. You just point your browser to the URL of your deployment. This section is about installing a Jitsi Meet suite on your server and hosting your own conferencing service.

Installing Jitsi Meet is a simple experience. For Debian-based system, following the quick-install document, which uses the package system. You can also see a demonstration of the process in this tutorial video.

For other systems, or if you wish to install all components manually, see the detailed manual installation instructions.

Download

Latest stable release release

You can download Debian/Ubuntu binaries:

You can download source archives (produced by make source-package):

Mobile apps

You can also sign up for our open beta testing here:

Development

For web development see here, and for mobile see here.

Contributing

If you are looking to contribute to Jitsi Meet, first of all, thank you! Please see our guidelines for contributing.

Embedding in external applications

Jitsi Meet provides a very flexible way of embedding in external applications by using the Jitsi Meet API.

Security

WebRTC does not (yet) provide a way of conducting multi-party conversations with end-to-end encryption. Unless you consistently compare DTLS fingerprints with your peers vocally, the same goes for one-to-one calls. As a result, your stream is encrypted on the network but decrypted on the machine that hosts the bridge when using Jitsi Meet.

The Jitsi Meet architecture allows you to deploy your own version, including all server components. In that case, your security guarantees will be roughly equivalent to a direct one-to-one WebRTC call. This is the uniqueness of Jitsi Meet in terms of security.

The meet.jit.si service is maintained by the Jitsi team at 8x8.

Security issues

We take security very seriously and develop all Jitsi projects to be secure and safe.

If you find (or simply suspect) a security issue in any of the Jitsi projects, please send us an email to security@jitsi.org.

We encourage responsible disclosure for the sake of our users, so please reach out before posting in a public space.

Acknowledgements

Jitsi Meet started out as a sample conferencing application using Jitsi Videobridge. It was originally developed by ESTOS’ developer Philipp Hancke who then contributed it to the community where development continues with joint forces!