Galène videoconference server

Galène (or Galene) is a videoconference server (an “SFU”) that is easy to deploy and that requires moderate server resources. It was originally designed for lectures, conferences and student tutorials, but is also useful for traditional meetings.

Galène has been used in production at two major universities (Université de Paris and Sorbonne Université) for lectures, practicals, seminars, and for staff meetings. It has been used to host two conferences (SOCS'2020 and JFLA'2021).

Galène's server side is implemented in Go, and uses the Pion implementation of WebRTC. The server is regularly tested on Linux/amd64 and Linux/arm64; it has also been shown to run on Linux/armv7 and Linux/mips (OpenWRT), and even on Windows. It should in principle be portable to other systems, including Mac OS X. The default client is implemented in Javascript, and works on recent versions of all major web browsers, both on desktop and mobile (but see the FAQ for caveats with specific browsers).

While traffic is encrypted and authenticated from sender to server and again from server to receiver, Galène does not perform end-to-end encryption: anyone who controls the server might, in principle, be able to access the data being exchanged. For best security, you should install your own server.

Galène's is not the only self-hosted WebRTC server. High-quality alternatives include Janus, Ion-SFU, and Jitsi.

Galène is free and open source software, subject to the MIT licence. Galène's development was partly supported by Nexedi.

Try it out

Go to and choose public (no password required).

Source code

git clone


Mailing list

Mailing list archives, Atom feed.

Please subscribe to the galene at mailing list. This list is both for user questions and development of Galène.


Get the source code by doing

git clone
then check the included INSTALL file.

Community-provided packages

These packages are provided by users, and have not necessarily been verified by Galène's author.

Related software


Authentication services

Alternate frontends and management software


Server features

The server is complete:

Client features

Default Javascript client

The web browser frontend is functional:

A number of features are currently only available as commands to be typed in the chat window (type /help for help).

Native Android client

A native Android client for Galene is in development. The web client is usually a better choice, but the native Android client supports screensharing, which is not possible in a mobile browser. The client is expected to work on all devices running Android 5 or later.

Third-party clients

Server robustness and scalability

For a typical lecture (100 students), Galène needs roughly 1/4 of a CPU core.

For one-to-many communication (lectures), the behaviour is linear, and Galène should be able to serve about 400 participants per core. For many-to-many communication (meetings), the behaviour is quadratic (the server load grows as the square of the number of participants), expect to be able to handle on the order of 20 participants in a single meeting on one core, 40 on four cores (and of course way more if some participants don't switch their camera on — we've had staff meetings with forty participants or so, but only a few had their cameras switched on at a given time).

Security model

Galène assumes that the server is trusted: all media is decrypted by the server and reencrypted before it is sent to the clients. This is, as far as I know, unavoidable with DTLS-SRTP, the security mechanism used by WebRTC (yes, I know about insertable streams.) On the other hand, since the client is not trusted, any bugs in the client code should in principle not create security issues. Thus, it is reasonable to build user-friendly clients using the unscrutable Javascript frameworks that web developers tend to like.

Be aware however that I am neither a security specialist nor a competent system administrator, and I may have gotten something wrong.

Common questions and known issues

Frequently Asked Questions.