Eclipse Amlen

Overview

Amlen is a self-hosted messaging server for IoT and web applications, with MQTT and JMS support. It is a strong fit when device traffic must coexist with JMS systems or legacy sensors; teams that need identity from multiple LDAP servers should look elsewhere.

Key features

MQTT versions 3 through 5 work over TCP/IP and WebSockets, and Amlen also supports JMS and conversion between the two. That interoperability can simplify messaging between connected devices and JMS applications. Client options include C, Java, Android, iOS, and JavaScript MQTT clients.

A protocol plug-in SDK lets teams add protocols, including for sensors that cannot speak MQTT. The Bridge can forward MQTT messages to another MQTT server or IBM Event Streams for IBM Cloud, with filtering, topic mapping, multiple forwarders, and REST-based configuration and monitoring. This breadth helps with integration and routing; it is more machinery than a team needs for a basic MQTT endpoint.

Security combines TLS profiles, user ID and password authentication validated against a configured LDAP server, and policies governing connections, topics, subscriptions, and queues. The single LDAP connection is a meaningful constraint: organizations consolidating identities from multiple directories cannot connect them separately. Administrators can manage message hubs and endpoints through the WebUI or REST Administration APIs.

Pricing

Eclipse Amlen: free. The free plan is the product's stated offering, with self-hosted deployment. No free trial is offered, and no paid tier is described. This makes it suitable for teams able to operate their own server without a subscription charge; configurable delivery guarantees provide flexibility, but no quota or seat limit is stated.

Platforms

Amlen is self-hosted, with API and web access and Android, iOS, and Linux platform support. The current stable release offers server and WebUI downloads for RHEL and AlmaLinux 8, 9, and 10. Its client support spans C, Java, Android, iOS, and JavaScript MQTT clients, so deployment platform and client platform are not the same consideration.

Who it's for

Amlen suits teams building IoT or web messaging systems that need MQTT and JMS interoperability, protocol extensions, or controlled forwarding between brokers. Its mature, enterprise production use makes it a candidate for larger deployments, but the single-directory identity constraint makes it a poor fit where users and groups must come from multiple LDAP servers. Support discussions are directed to Eclipse IoT Matrix channels.

Pros and cons

• Pro: MQTT-to-JMS conversion and support for both protocols can connect device messaging with JMS applications.
• Pro: Protocol plug-ins and Bridge filtering, topic mapping, and multiple forwarders provide options for legacy devices and message routing.
• Pro: Connection, topic, subscription, and queue policies let administrators restrict different messaging actions.
• Con: One LDAP server connection limits identity integration for organizations using multiple directories.
• Con: Self-hosted deployment means teams need to run the server themselves; this is not a hosted service option.

Alternatives

Message Broker Software is the broader category to browse. Consider Lightstreamer if a freemium option with a free trial and a demo license capped at 20 concurrent client connections better matches the evaluation or deployment need. EMQX is another freemium option with a serverless plan that includes up to 1,000 connections and usage-based charges beyond its monthly free quota.

Faye is a free Apache 2.0-licensed alternative. SocketCluster is a free, MIT-licensed self-hosted option with no paid plans listed. TIBCO FTL offers a free Community Edition download as well as a paid Enterprise Edition. Apache Artemis is a free, self-hosted broker requiring Java 17 or later. Apache Qpid Broker-J is a free option with no paid plan or usage limits stated. Apache RocketMQ is free and licensed under Apache 2.0.

Verdict

Choose Eclipse Amlen if you need a self-hosted MQTT server that can bridge MQTT and JMS, extend protocols, and apply granular messaging policies without a subscription cost. Look elsewhere if identity integration across multiple LDAP servers is essential, or if you do not want to operate your own server.