Spreed alternatives and similar software solutions
Based on the "Mumble" category.
Alternatively, view Spreed alternatives based on common mentions on social networks and blogs.
9.1 9.9 L3 Spreed VS SynapseA server for Matrix, an open standard for decentralized persistent communication.
6.7 9.7 L1 Spreed VS RetroShareSecured and decentralized communication system. Offers decentralized chat, forums, messaging, file transfer.
4.5 6.2 Spreed VS Spectrum 2Spectrum 2 is an open source instant messaging transport. It allows users to chat together even when they are using different IM networks.
3.8 0.0 L5 Spreed VS PushjetA self hosted push notification service built with a simple API making sending notifications easy.
3.2 7.5 L3 Spreed VS RingFree software for universal communication which respects freedoms and privacy of its users.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of Spreed or a related project?
Spreed WebRTC implements a WebRTC audio/video call and conferencing server and web client.
The latest source of Spreed WebRTC can be found on GitHub. If you are a user, just wanting a secure and private alternative for online communication make sure to check out the Spreedbox, providing a ready to use hardware with Spreed WebRTC included.
Spreed WebRTC compiles directly to native code and has no external runtime dependencies. See here for details.
If you got spreed-webrtc from the git repository, you will first need
to run the included
autogen.sh script to generate the
Configure does try to find all the tools on your system at the standard locations. If the dependencies are somewhere else, add the corresponding parameters to the ./configure call.
$ ./configure $ make
There are several make targets available. Get Go external dependencies at
least once with
make get, all the other targets depend on this.
$ make get $ make assets $ make binary
-c="./server.conf": Configuration file. -cpuprofile="": Write cpu profile to file. -h=false: Show this usage information and exit. -l="": Log file, defaults to stderr. -memprofile="": Write memory profile to this file. -v=false: Display version number and exit.
An example configuration file can be found in server.conf.in.
Connect to the server URL and port with a web browser and the web client will launch.
To build styles and translations, further dependencies are required. The source tree contains already built styles and translations, so these are only required if you want to make changes.
The following Node.js modules are required, these may be installed
locally by running
npm install from the project root. Consult the
package.json file for more details.
Styles can be found in src/styles. Translations are found in src/i18n. Each folder has its own Makefile to build the corresponding files. Check the Makefile.am templates for available make targets.
adding the query parameter
debug to your url
Running server for development
Copy the server.conf.in to server.conf.
The server runs on http://localhost:8080/ per default.
Running for production
Spreed WebRTC should be run through a SSL frontend proxy with
support for Websockets. Example configuration for Nginx can be
In addition, for real world use, one also needs a STUN/TURN server configured (with shared secret support).
See https://github.com/coturn/coturn for a free open source TURN server implementation. Make sure to use a recent version (we recommend 3.2). Versions below 2.5 are not supported.
For WebRTC usage, be sure to enable long-term credentials, fingerprinting, and set the realm. See https://github.com/coturn/coturn/wiki/turnserver#webrtc-usage for more information.
Running with Docker
We provide official Docker images at https://hub.docker.com/r/spreed/webrtc/. Of course you can build the Docker image yourself as well. Check the Dockerfiles in this repository for details and instructions.
Use the following command to run a Spreed WebRTC Docker container with the default settings from our official Spreed WebRTC Docker image.
docker run --rm --name my-spreed-webrtc -p 8080:8080 -p 8443:8443 \ -v `pwd`:/srv/extra -i -t spreed/webrtc
Chrome should work out of the box.
As of Firefox >= 36 you must append the domain being used to the allowed domains
to access your screen. You do this by navigating to
about:config, search for
'media.getusermedia.screensharing.allowed_domains', and append the domain
to the list of strings. You can edit the field simply by double clicking on it.
Ensure that you follow the syntax rules of the field. If you are using an
url, simply append
ip to the list. Also ensure that you are using
otherwise permission will be denied to share your screen. You do not need to restart
or reload in order for it to take affect.
- "Fork" develop branch.
- Create a feature branch.
- Make changes.
- Do your commits (run
make jshintbefore commit).
- Send "pull request" for develop branch.
Spreed WebRTC uses the AGPL license, see our
*Note that all licence references and agreements mentioned in the Spreed README section above are relevant to that project's source code only.