Router Configuration

Routers are the core facilities of, responsible for routing WAMP remote procedure calls between Callers and Callees, as well as routing WAMP publish-subscribe events between Publishers and Subscribers.

A instance will usually be running at least one Router, unless is used solely to run application components in Workers or Guests.

A Router is configured as a Worker, more precisely a Native Worker, process of type == "router":

   "workers": [
         "type": "router",
         "options": {
            // router options go here
         "realms": [
            // realms managed by this router
         "transports": [
            // transports run by this router
         "components": [
            // app components running side-by-side with this router

For the available options with Routers, please see

For configuration of realms, transports and components, have a look here





Optional router ID (default: "router<N>")


Must be "router".


Please see Native Worker Options .


Please see Router Realms .


Please see Router Transports .


A list of components. Please see below.


Not yet implemented.

Router components are either plain Python classes:




Optional component ID (default: "component<N>")


Must be "class".


The realm to join with the component.


The authrole under which to attach the component.


Please see below.


The fully qualified Python classname to use.


Arbitrary custom data forwarded to the class ctonstructor.