Apache Qpid is a messaging broker that implements the latest AMQP specification, providing transaction management, queuing, distribution, security, management, clustering, federation, heterogeneous multi-platform support, and much more. It is extremely fast and aims to be 100% AMQP Compliant.
pyBit uses AMQP to create a distributed, cross-platform buildd toolkit to build packages using a collection of buildds, direct from various VCS clients. It is intended to support rapidly evolving software collections, and can support multiple VCS frontends and multiple build backends. Cross building is expected to be supported for some backends. The initial backend uses dpkg for Debian. pyBit includes support for cancelling selected builds and using multiple buildd clients per architecture, per platform, and per suite.
The Clacks Framework enables implementators to abstractly manage infrastructure entities, such as users, groups, machines and structure items. These are freely defineable and mappable to various backends like LDAP or MongoDB. Additionally it can handle joined clients, collect inventory data, and manage these clients in various ways. All information, API, and events are exposed on an AMQP message bus, and can be used by shell scripts, Web GUIs, etc.
Zato is an Enterprise Service Bus (ESB) and app server written by pragmatists for pragmatists. It provides an HA load-balancer, hot-deployment, and hot-reconfiguration almost everywhere (forget server restarts). It has a browser-based GUI, CLI, and API (forget XML configuration). It supports many protocols, industry standards, and data formats, including HTTP, JSON, SOAP, REST, AMQP, JMS WebSphere MQ, ZeroMQ, Redis, SQL, and FTP.