SwiftMQ goes Open Source

We strive to put SwiftMQ on a solid foundation and to create a strong, collaborative and thriving community. This is the reason why we have released our full featured base products under the open source Apache 2.0 license, effective with release 12.


We provide 2 open source products:

  • SwiftMQ Client
  • SwiftMQ Community Edition (CE)

Our open source products are licensed under the Apache 2.0 license. The sources are available on GitHub.

Based on SwiftMQ CE we provide 2 commercial products:

  • SwiftMQ Universal Edition (UR)
  • SwiftMQ High Availability Edition (HA)

The prices of the commercial products are the same as before.

All editions now have docker support. SwiftMQ CE is also available on Docker Hub while the UR/HA docker images are available from this site as a download. SwiftMQ Client is available as artifact on Maven Central.


SwiftMQ Client and SwiftMQ CE are supported by the community. We use Stackoverflow and tag "swiftmq". This tag is monitored by IIT Software. Support is not guaranteed.

SwiftMQ UR and HA are professional supported by IIT Software, just like before.

Discontinued Products

The following products have been discontinued:

  • SwiftMQ AMQP Router
  • SwiftMQ Dashboard

There will be an alternative product for SwiftMQ Dashboard which will be released from another company soon.

Discontinued Features

The following features have been removed from SwiftMQ:

  • JEE Resource Adapter (App Server)
  • SNMP Extension Swiftlet
  • Portmapper Extension Swiftlet
  • Amazon SQS Extension Swiftlet
  • Multicast Extension Swiftlet
  • LDAP Authentication Swiftlet

Major Changes

To make SwiftMQ more docker friendly we have changed the data structure of our distributions. All dynamic data is now under a "data/" folder and can be easily mapped into a docker container.

The CE and UR distributions now contain the configuration for a single router (default name "router") instead of 2 routers.

We have added a new feature called "preconfig". It is now possible to store all node specific configurations such as router name, queues, topics, listeners etc in so-called preconfig files. These files are applied to a standard router configuration during startup and turns it into a node specific configuration. This is especially useful when using docker or SwiftMQ HA.