MQTTX Web client...for developer....access only on specific topics (data domain)

[mmorath]

We’re planning to deploy MQTTX Web as a browser-based MQTT client inside a Kubernetes cluster. The goal is to make it available to developers working on different systems.

We’ve read that MQTTX Web offers:

TLS support with client certificates

A full GUI for working with topics, subscriptions, and publishing

Docker-based deployment

Infrastructure-as-Code friendly setup (e.g., Helm or Kustomize)

🔗 https://mqttx.app/web

Our use case is to make MQTTX Web available to developers in a secure way. We want to restrict access to certain topics based on client certificates – i.e., access control would be managed via certificate identity, and not within the web app itself.

However, a colleague of mine claims that MQTTX Web doesn't support this kind of setup (i.e., mutual TLS and cert-based restrictions).

Could someone from the community confirm:

Does MQTTX Web support TLS/mTLS with client certificates in the browser?

Is it commonly used in Kubernetes environments, deployed via Helm/Kustomize?

Has anyone implemented certificate-based topic restrictions, possibly with EMQX or another broker?

Any advice, examples, or best practices would be highly appreciated!