Going Open Source Part 1: Palava Machine

We at palava believe that WebRTC is a very promising technology with the potential to change the shape of the web. We built palava to get an impression of how well this technology already works. The platform was launched back in May and we collected a lot of encouraging feedback. We also discussed how to take palava further with the following result:

palava is supposed to be a simple and free platform for decentralized and secure communication. Nevertheless, there is still a (centralized) server component (“signaling”) that manages who wants to talk to whom and which kind of media to exchange. This means, in some way, most webrtc application will be centralized and you have to trust the provider (e.g. us) that we do not save any meta data of how you are using the service.

Open Source

This is one of the reasons, why we are open sourcing palava and all our webrtc libraries. It enables you to host your own video communication platform. We will continue to provide an instance at palava.tv and are currently founding a non-profit organization that will run the infrastructure for palava. More information our plans regarding the non-profit in a future blog post.

We have begun open sourcing our stack with an essential part of webrtc infrastructures: The signaling. We have built our palava signaling component using the Ruby programming language and the Redis key-value store. It is called PalavaMachine and you can find it on github.

Within the next weeks, we will also relase our JavaScript client library and the web application code. Happy hacking and mail us for questions!

Best,
the palava team.

PS: Jan & Marius are building a new WebRTC service called signaling.io. If you do web development and plan to use WebRTC in a future project, you might want to get notified when the service launches!