About > Features > Roadmap


Crossbar.io is being actively developed. Here we want to give an overview of the current thinking of the core team of developers regarding where we want to take the project.

The bulk of the development work on Crossbar.io is being done by developers from Tavendo, a German company.

We at Tavendo fully stand behind Crossbar.io as an open source software (AGPL licensed), and will continue to both improve existing functionality and add new features.

We also want to offer commercial services and additional features that provide the peace of mind that professional users require and which add capabilities demanded in commercial deployments.

Overall we are focusing on the Internet of Things space as a main application for Crossbar.io.

We are aware that Crossbar.io as messaging middleware has many uses. All that the focusing means is that features required for use in the IoT take priority in our work queues. You can, of course, send us a pull request for other features!

Open Source and Commercial

The basic distinction between the open source Crossbar.io and the commercial offerings around it, as we see it at the moment, is:

  • Crossbar.io run as a single node with static configuration is open source
  • Dynamic configuration, remote monitoring, high availability and clustering are going to be part of a commercial offering

The decision between what we add to the open source project and what may end up as a commercial add-on will generally made based on this.

Crossbar.io itself is going to remain a powerful tool, and will continue to develop.

The commercial services and features will further extend its utility, and enable us to continue to support Crossbar.io's development.

Open Source Roadmap

Based on discussions with users in the IoT space, integration with other protocols is very important. Especially in the field of industrial use existing systems need to be combined with newer technology. MQTT was frequently mentioned in this context.

We have working code for a MQTT bridge and this should be released soon. The MQTT bridge is a full MQTT broker which also allows MQTT messages to trigger WAMP events and vice versa. This means not just easy integration into existing projects which use MQTT, but one central router to handle both WAMP and MQTT traffic.

Combined with the existing REST bridge this means that applications using Crossbar.io can integrate an even wider range of non-WAMP services and devices.

Commercial Roadmap

We are currently offering a Development Acceleration Package for applications under development which use Crossbar.io. This includes

  • support from core Crossbar.io developers for e.g. application architecture regarding messaging and Crossbar.io configuration
  • a commercial license for Crossbar.io
  • access to the alpha version of the Crossbar.io DevOps Center (CDC)

The Crossbar.io DevOps center is an online service that Crossbar.io instances connect to. This is presently in a closed alpha test (contact us if you#re interested) and allows you to remotely and dynamically configure Crossbar.io nodes from your code.

The next thing to be released as part of this will be a monitoring dashboard in the browser which allows you to have a live view of key node metrics.

Planned features for the CDC are:

  • a CLI for managing Crossbar.io nodes
  • high availability by pairing two or three Crossbar.io nodes
  • clustering of Crossbar.io nodes
  • router workers on a node using multiple cores

We are planning on offering a free tier of the CDC.

You can find out more about the upcoming commercial offering at Crossbario.com.

Feedback and Participation

We welcome all input regarding the project direction. Contributions which are well-argued (e.g. have a use case for a proposed feature and sketch out what changes would be necessary to get there) have a better chance of influencing the project than mere one-line suggestions.

You could also implement things yourself. In this case, please contact us before you start coding (except for trivial things). Sudden large pull requests for features never previously discussed are not the best of ideas!

We have limited resources for development work and set our own priorities. That said, we do custom work and a great way to get a feature you really want may be to contract Tavendo directly to do the development. You may do so by mailing service@tavendo.de.