Documentation > FAQ


Frequently asked questions with, Autobahn and WAMP.

The WAMP ecosystem

What is the relationship between WAMP, Autobahn and

WAMP is an open source protocol which provides RPC and PubSub messaging patterns.

The Autobahn project provides WAMP implementations in multiple languages. builds on Autobahn|Python, one of the Autobahn projects, and provides a much larger set of functionality to make it into a powerful router for application messaging.

What is WAMP?

WAMP (Web Application Messaging Protocol) is a protocol which provides both Remote Procedure Calls (RPC) and Publish & Subscribe (PubSub) messaging patterns. All clients can be both publishers and subscribers, callers of remote procedures and offer remote procedure endpoints. A WAMP router connects the clients.

WAMP enables distributed, multi-client and server applications. It is an open protocol, and several independent implementations exist.

WAMP has WebSocket as a preferred transport.

What is Autobahn?

The Autobahn project provides open-source WebSocket and WAMP implementations for several programming languages. WAMP implementations are for client roles implementations.

What is builds on Autobahn|Python. It adds the full set of advanced WAMP router functionality, as well as things like an integrated Web server, hosting of application components or support for various authentication methods.
Applications developed with can use any WAMP client library. This, obviously, includes the Autobahn libraries.


What does open-source license mean for me when I use it for a project?

The license (AGPL v3) does not have any effect on your application. The APGL only affects code which is joined to a AGPL licensed project's code.

When using for an application, your application code just sends and receives WAMP messages, which routes. This does not join your code to the code of This applies irrespective of where you run your code. Using the possibility to host application components with does not join your code with

Your code remains yours, and you can license it in whichever way you want.

If you need further assurance, you can email us at for a signed letter asserting our view on the license.

What is the license for the application templates?

We license all examples and other materials that you can use in creating your own applications as liberally as possible.

In the case of the application templates, these are licensed either under the BSD 2-clause license or the Apache 2.0 license. Both allow you to use the code in your own applications, irrespective of which license you are using. And yes, this includes commercial & closed source.

Modifying and Contributing

Can I hack to fit my own needs?

Like all open source licenses, the AGPL gives you the right to modify the code: to fix bugs, optimize things, add features, or anything else you need or feel like doing.

When you modify, then you need to provide access for others to your modified code if

  • you distribute the modified code to any third party
  • you run the modified code on a server accessible to any third party

A 'third party' would usually be anybody else but you. An exception is when you are working for a company - use purely inside the company does not trigger the requirement to provide access to your code.

What this means is that you cannot use as the basis for developing closed source software (except for when you are its only user).

I want to contribute to - what do I need to do?

There are full instructions for how to contribute.

The short version: is hosted on GitHub, so you need to be familiar with the git development model.

Additionally, before we can accept your first contribution, you need to sign a Contributor Assignment Agreement (CAA) and mail this to us.

This is needed in order for the project to have all necessary rights to the code, e.g. to be able to switch licenses in the future.


Can I integrate a non-WAMP application into my WAMP application?

It is possible to have a WAMP component which communicates with your non-WAMP application (component) and does WAMP messaging based on this. How complex this is depends on the specifics of the use case, e.g. the protocol.

We do provide components for communicating with other applications over HTTP/POST requests- see the documentation, as well as integration for MQTT clients via a full MQTT broker

remote management for
Test remote management for
Community Chat