AyaiMQ broker · Rev. Beta · managed service · free during beta
Managed MQTT,
done right.
A fully managed MQTT broker for your whole estate. Spin up an isolated cluster, issue per-device credentials, and watch messages flow in a built-in web client. UDMI controllers and devices connect out of the box, and there are no servers to run.
- Protocol
- MQTT 3.1.1 · 5.0
- UDMI
- ready · included
- Sign-in
- key-pair · password
- Isolation
- per-tenant
Fig 1A cluster, connected
live sample of a running broker§ 1Specifications
what the broker guarantees| Protocol | Standard MQTT (3.1.1 and 5). Works with any MQTT client or library. |
|---|---|
| UDMI | Built in. UDMI devices and controllers connect directly, at no extra cost. |
| Connection | Encrypted connections everywhere, plus WebSocket for browsers. |
| Device sign-in | A username and password, or a secure key pair for controllers. |
| Permissions | Decide exactly which topics each device can send to or receive from. |
| Isolation | Your broker is walled off from every other customer. |
| Delivery | Reliable delivery, with retained values and last-will, so nothing is lost. |
| Capacity | Thousands of devices connected at once. |
| Credentials | Passwords are encrypted at rest, never stored in the clear. |
| Audit | A plain record of every connection, sign-in and change. |
| Hosting | Fully managed by Logicboks. Nothing for you to run or patch. |
§ 2Operation
connected in minutes, not days- 01
Create a cluster
One click gives you a managed broker with its own endpoints. Nothing to host.
cluster: production-a1 · broker.ayaimq.com - 02
Issue a credential
Generate a key-pair for a controller or a password for a service, scoped to its topics.
svc-ingest · publish plant/# - 03
Connect and watch
Point the device at the endpoint and watch messages arrive in the web client.
mqtts://broker.ayaimq.com:8883
§ 3Engineering notes
the fine print, up frontEvery broker endpoint is TLS only. Plaintext 1883 is never exposed.
Each cluster is walled off by mountpoint and row-level security. A client cannot cross into another tenant.
Broker passwords are hashed on the auth path and never returned. Keys rotate without downtime.
Authentication and ingest are rate limited per tenant, with an admin-set ceiling and an alarm.
Credential and cluster changes are written to an audit log you can read per cluster.
Export or delete a tenant on request. Standard GDPR handling, no retention games.
§ 4How AyaiMQ compares
against the usual optionsBring your devices online.
Create a cluster, add credentials, and watch your messages flow. Access is invite-only while we are in beta, and free.