Version Build Status Coverage Docs

Open-source (MIT) real-time framework for Web, Mobile & Internet of Things.

Autobahn|Python is part of the Autobahn project and provides open-source implementations of

in Python 2 and 3, running on Twisted or asyncio.

Autobahn Features

WebSocket allows bidirectional real-time messaging on the Web while WAMP provides applications with high-level communication abstractions (remote procedure calling and publish/subscribe) in an open standard WebSocket-based protocol.

Autobahn|Python features:

...and much more.

Further, Autobahn|Python is written with these goals:

  1. high-performance, fully asynchronous and scalable code
  2. best-in-class standards conformance and security

We do take those design and implementation goals quite serious. For example, Autobahn|Python has 100% strict passes with AutobahnTestsuite, the quasi industry standard of WebSocket protocol test suites we originally created only to test Autobahn|Python ;)

For (hopefully) current test reports from the Testsuite see


In the following, we will just refer to Autobahn instead of the more precise term Autobahn|Python and there is no ambiguity.

What can I do with Autobahn?

WebSocket is great for apps like chat, trading, multi-player games or real-time charts. It allows you to actively push information to clients as it happens. (See also Automatically Run All Examples)

ascii-cast of all WAMP demos running

Further, WebSocket allows you to real-time enable your Web user interfaces: always current information without reloads or polling. UIs no longer need to be a boring, static thing. Looking for the right communication technology for your next-generation Web apps? Enter WebSocket.

And WebSocket works great not only on the Web, but also as a protocol for wiring up the Internet-of-Things (IoT). Connecting a sensor or actor to other application components in real-time over an efficient protocol. Plus: you are using the same protocol to connect frontends like Web browsers.

While WebSocket already is quite awesome, it is still low-level. Which is why we have WAMP. WAMP allows you to compose your application from loosely coupled components that talk in real-time with each other - using nice high-level communication patterns (“Remote Procedure Calls” and “Publish & Subscribe”).

WAMP enables application architectures with application code distributed freely across processes and devices according to functional aspects. Since WAMP implementations exist for multiple languages, WAMP applications can be polyglot. Application components can be implemented in a language and run on a device which best fit the particular use case.

WAMP is a routed protocol, so you need a WAMP router. We suggest using, but there are also other implementations available.


Show me some code!

A sample WebSocket server:

from autobahn.twisted.websocket import WebSocketServerProtocol
# or: from autobahn.asyncio.websocket import WebSocketServerProtocol

    class MyServerProtocol(WebSocketServerProtocol):

       def onConnect(self, request):
           print("Client connecting: {}".format(request.peer))

       def onOpen(self):
           print("WebSocket connection open.")

       def onMessage(self, payload, isBinary):
           if isBinary:
               print("Binary message received: {} bytes".format(len(payload)))
               print("Text message received: {}".format(payload.decode('utf8')))

           ## echo back message verbatim
           self.sendMessage(payload, isBinary)

       def onClose(self, wasClean, code, reason):
           print("WebSocket connection closed: {}".format(reason))

Complete example code:

Introduction to WebSocket Programming with Autobahn:

A sample WAMP application component implementing all client roles:

from autobahn.twisted.wamp import ApplicationSession
# or: from autobahn.asyncio.wamp import ApplicationSession
class MyComponent(ApplicationSession):

   def onJoin(self, details):

       # 1) subscribe to a topic
       def onevent(msg):
           print("Got event: {}".format(msg))
       yield self.subscribe(onevent, 'com.myapp.hello')

       # 2) publish an event
       self.publish('com.myapp.hello', 'Hello, world!')

       # 3) register a procedure for remoting
       def add2(x, y):
           return x + y
       self.register(add2, 'com.myapp.add2');

       # 4) call a remote procedure
       res = yield'com.myapp.add2', 2, 3)
       print("Got result: {}".format(res))

Complete example code:

Introduction to WAMP Programming with Autobahn:

Where to start

To get started, jump to Installation.

For developers new to asynchronous programming, Twisted or asyncio, we’ve collected some useful pointers and information in Asynchronous Programming.

For WebSocket developers, WebSocket Programming explains all you need to know about using Autobahn as a WebSocket library, and includes a full reference for the relevant parts of the API.

WebSocket Examples lists WebSocket code examples covering a broader range of uses cases and advanced WebSocket features.

For WAMP developers, WAMP Programming gives an introduction for programming with WAMP in Python using Autobahn.

WAMP Examples lists WAMP code examples covering all features of WAMP.

Get in touch

Development of Autobahn takes place on the GitHub source repository.


We are open for contributions, whether that’s code or documentation! Preferably via pull requests.

We also take bug reports at the issue tracker.

The best place to ask questions is on the mailing list. We’d also love to hear about your project and what you are using Autobahn for!

Another option is StackOverflow where questions related to Autobahn are tagged “autobahn” (or “autobahnws”).

The best way to Search the Web for related material is by using these (base) search terms:

You can also reach users and developers on IRC channel #autobahn at

Finally, we are on Twitter.


Autobahn is an open source project, and hosted on GitHub. The GitHub repository includes the documentation.

We’re looking for all kinds of contributions - from simple fixes of typos in the code or documentation to implementation of new features and additions of tutorials.

If you want to contribute to the code or the documentation: we use the Fork & Pull Model.

This means that you fork the repo, make changes to your fork, and then make a pull request here on the main repo.

This article on GitHub gives more detailed information on how the process works.

In order to run the unit-tests, we use Tox to build the various test-environments. To run them all, simply run tox from the top-level directory of the clone.

For test-coverage, see the Makefile target test_coverage, which deletes the coverage data and then runs the test suite with various tox test-environments before outputting HTML annotated coverage to ./htmlcov/index.html and a coverage report to the terminal.

There are two environment variables the tests use: USE_TWISTED=1 or USE_ASYNCIO=1 control whether to run unit-tests that are specific to one framework or the other.

See tox.ini for details on how to run in the different environments.

Release Testing

Before pushing a new release, three levels of tests need to pass:

  1. the unit tests (see above)
  2. the [WebSocket level tests](wstest/
  3. the [WAMP level tests](examples/ (*)

> (*): these will launch a router for testing


Please see Site Contents for a full site-map.