Control planes

Three ways to drive the same agent. They are adapters over one shared CommandHandler, so any of them can do anything the others can — no feature drifts between transports.

AdapterBest forOn by default
HTTPLocal management, debugging, Prometheusyes (loopback)
MQTTIoT platforms, constrained devices, existing brokersno

You can run several at once — HTTP on loopback for local debugging while MQTT carries fleet commands is a common combination:

keystone --http 127.0.0.1:8080 \
         --mqtt-broker tls://broker.acme.com:8883 --mqtt-device-id edge-001

  • HTTP

    The REST API, endpoint by endpoint.

  • MQTT

    Topics, QoS, and last-will for presence. {class=“children children-type-flat children-sort-”}