A fully managed MQTT broker at the edge.
mTLS in, inspected in flight, sharded at scale.

Every panel below is live telemetry from a running deployment: MQTT over secure WebSocket, terminated and authenticated at the CDN edge, routed through the Sentinel L7 proxy into sharded brokers with inline threat inspection. Right now it is holding a sustained six-figure connection load.

TRANSPORTMQTT 3.1.1 / WSS

EDGEmTLS + JWT

INSPECTIONinline L7

QoS1

Performance/api/metrics · 2s

Concurrent connections

—

held through the edge

Message throughput

—

msgs/sec in + out

Messages inspected

—

scanned inline / sec

Delivery p95

—

end-to-end, 1:1 pattern

End-to-end delivery latencyby message pattern · publish → receive

Pattern	p50	p95	p99	delivered / sec
measuring…

Securityinline inspection · live

Inspection rate

—

msgs scanned/sec

Anomaly rate

—

rate deviations/sec

Threats blocked

—

malicious payloads

Threat feed

Architectureclient → edge → sentinel → shards

Try it · in-browser WSS clientreal MQTT over WSS through the edge

connection idle

round-trip — ms

msgs 0

How the round-trip works

The browser fetches a short-lived JWT from /jwt, opens an MQTT-over-WSS session to /wss at the edge, subscribes to its own client-id topic, then publishes a stamped message to that same topic. Because publish and receive share one clock, the measured round-trip is drift-free end-to-end latency through the full path.

The device may only touch its own topic — the same per-identity policy the platform enforces for every connected client.

jwt not fetched

A fully managed MQTT broker at the edge.mTLS in, inspected in flight, sharded at scale.

A fully managed MQTT broker at the edge.
mTLS in, inspected in flight, sharded at scale.