# Installer emqx avec Homebrew
Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de emqx pour les workflows d'agents IA.
## installation
```sh
sudo av install brew:emqx
```
Commandes d'installation supplémentaires:
### macOS
- Homebrew (100%):
```sh
brew install emqx
```
Preuve: local Homebrew formula metadata
## Faits du paquet
- **Clé du paquet:** brew:emqx
- **Gestionnaire de paquets:** Homebrew
- **Version:** 5.8.8
- **Résumé source:** MQTT broker for IoT
- **Page d'accueil:**
- **Dépôt:**
- **Généré:** 2026-08-03T19:37:03+00:00
## exécutables
- emqx (alias)
- emqx-5.8.8 (alias)
- emqx_cluster_rescue (alias)
- emqx_ctl (alias)
- emqx_ctl-5.8.8 (alias)
- emqx_fw (alias)
- install_upgrade.escript (alias)
- install_upgrade.escript-5.8.8 (alias)
- no_dot_erlang.boot (alias)
- node_dump (alias)
- nodetool-5.8.8 (alias)
## Comportement d'installation
- Bouteille: non disponible
## Version et fraîcheur
- page générée: 2026-08-03
- version du gestionnaire: 5.8.8
## Historique du projet et usages
EMQX is an Erlang-based MQTT broker and IoT messaging platform for high-scale device connectivity, MQTT protocol support, clustering, rules, data integrations, and operational management.
### Historique du projet
EMQ's tenth-anniversary post says EMQX was released as an open-source project on GitHub on December 17, 2012. The same source frames its origin around Erlang, MQTT, and open source, and says development continued through the 2010s as MQTT became a default protocol for IoT messaging.
The official history highlights several product milestones: early MQTT 3.1 and 3.1.1 compatibility, EMQX 3.0 in 2018 with full MQTT 5.0 server support, EMQX 4.0 in 2020 with a built-in SQL-based rule engine, and EMQX 5.0 with larger-scale clustering, MQTT over QUIC, and 100M+ connection testing.
The README describes EMQX as a platform rather than only a broker, with support for MQTT 5.0, 3.1.1, and 3.1, plus MQTT-SN, CoAP, LwM2M, and MQTT over QUIC. It also documents the 5.9.0 licensing/product change that unified features from the previous open-source and enterprise editions under BSL 1.1.
### Historique d'adoption
The anniversary post gives the clearest official adoption snapshot: more than 10K GitHub stars, more than 20M downloads, more than 20,000 enterprise users, and more than 30,000 active cluster deployments per month at the time of that post.
EMQX's commercial adoption story is also official: EMQ says the company opened in 2017 in response to enterprise users deploying EMQX at scale, and the anniversary post cites over 400 customers and over 70 Fortune 500 companies using EMQX in IoT, IIoT, connected-vehicle, and other mission-critical applications.
### Modes d'utilisation
Package users run EMQX as a broker service, commonly exposing MQTT ports, the Dashboard, and HTTP APIs. The official README shows Docker startup, Kubernetes operator documentation, downloads for self-managed installs, and build-from-source instructions.
Configuration became more HOCON-oriented in EMQX 5. The official configuration docs describe `etc` as the static configuration directory, `data/configs` as the dynamic runtime configuration directory, `base.hocon` for configuration-as-code, `cluster.hocon` for changes persisted through Dashboard/API/CLI, and `emqx.conf` for backward-compatible immutable settings.
In deployed systems, EMQX is commonly used as the MQTT ingress and routing layer for IoT data, with rules and bridges sending messages to Kafka, RabbitMQ, PostgreSQL, MySQL, MongoDB, Redis, ClickHouse, cloud messaging services, webhooks, and observability systems.
### Pourquoi les passionnés de paquets s'y intéressent
EMQX is a heavier package-manager entry than most CLIs in this batch: it ships a broker, management commands, Erlang runtime expectations, configuration layers, a dashboard, and service-style deployment behavior. For package maintainers, it sits closer to Redis, RabbitMQ, or Mosquitto than to a single-purpose command.
It matters to package nerds because it exposes the messy but useful intersection of package managers and distributed systems: local development installs, service supervision, data directories, versioned config migration, and network ports all have to line up before the binary is useful.
### Chronologie
- 2012: EMQX released as an open-source project on GitHub on December 17.
- 2017: EMQ opened as a company after enterprise deployment demand grew.
- 2018: EMQX 3.0 released with complete MQTT 5.0 server support.
- 2020: EMQX 4.0 introduced a built-in SQL-based rule engine.
- 2022: EMQX 5.0 arrived with 100M+ connection testing and MQTT over QUIC highlighted by EMQ.
- v5.9.0: EMQX unified prior open-source and enterprise features under BSL 1.1.
### Related projects
- Related EMQ projects and surfaces include EMQX Cloud, the EMQX Kubernetes Operator, MQTTX, the EMQX rule engine and data integrations, and the broader MQTT broker ecosystem that includes Mosquitto, VerneMQ, HiveMQ, and RabbitMQ MQTT plugins.
### Sources
-
-
-
-
## Notes de sécurité
formula declares a Homebrew service. infrastructure mutation or orchestration signal.
- **Risque Geiger:** orange / moyen
- formula declares a Homebrew service
- infrastructure mutation or orchestration signal
## Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
## Configuration files
- Unix: etc/emqx.conf, etc/base.hocon, etc/cluster.hocon
## Combined YAML source
View the package source record on GitHub. [combined/emqx.yml](https://github.com/mxcl/pkgdb/blob/main/combined/emqx.yml)
## Sources
- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph