Communication Infrastructure for the AI Era
One binary, one broker, no external dependencies. Native MQTT, Kafka, NATS, and AMQP on a unified storage layer — one message, consumed by any protocol.
mq9Communication layer for AI Agents · Agent mailbox — send now, receive when online→Publish via MQTT, consume natively with MQTT, Kafka, NATS, and AMQP — one data store, zero bridging, zero copying
Not protocol silos stitched together — unified at the architectural level
Native Agent Infrastructure
MQTT in / Kafka out
Full Kafka Compatibility
Unified Edge and Cloud
NATS Pure In-Memory Routing
Native AMQP Support
Compute, storage, and coordination fully separated — each layer scales independently, delivered as a single binary
No GC, stable and predictable memory, no periodic spikes — consistent from edge devices to cloud clusters
All protocols share one storage engine — data written once, consumed by any protocol, no duplication
MQTT 3.1/3.1.1/5.0, Kafka, NATS, AMQP natively implemented — full protocol semantics, not emulated
Single binary, zero dependencies, offline buffering with auto-sync — same runtime from edge to cloud
NATS-based $mq9.AI.API.* extension — native Agent registration, discovery, invocation, and orchestration
Memory / RocksDB / File, per-Topic configuration, automatic cold data tiering to S3
Break the "concurrency = partition count" limit — consumers scale elastically at any time
Unified multi-tenancy across all protocols — full data isolation and independent permissions per tenant
Single binary, zero external dependencies, built-in Raft consensus, ready out of the box
Single binary, zero external dependencies, one command per node