Product and integration
Name the broker workflow, client library, protocol version, transport, and environment involved.
Contact RunMQTT
Bring the broker context; we will help route the problem
Ask about a product workflow, MQTT integration, account, billing state, or reproducible bug. Choose a private or public channel based on whether the report contains sensitive operational context.
Contact channels
Choose a channel that matches the report
Use email for account or sensitive context, discussions for open questions, and issues for reproducible product defects.
Email Support
Email gateway
Technical support via email
support@runmqtt.comCommunity Discussions
Discussion board
Ask product and integration questions in public
Open discussionsBug Reports
Issue tracker
Report reproducible bugs and integration failures
Open issuesDocumentation
Documentation portal
Setup guides, billing flow notes, and deployment docs
Read docsUseful context
Make the first report actionable
A focused report shortens diagnosis without exposing production secrets.
Reproducible defect
Share a minimal sequence, expected result, actual result, timestamps, and sanitized logs.
Sensitive or account-specific
Use email for billing, account ownership, private topology, or a security concern.
Clear follow-up
Provide a reply address and state whether the issue blocks testing, rollout, or production operation.
Affected page, API, broker, client, or billing workflow.
Client library, MQTT version, transport, and runtime versions.
Smallest sequence that reproduces the behavior.
Sanitized error codes, timestamps, logs, and screenshots.
Current impact and any safe workaround already tested.
No passwords, tokens, private keys, or customer payloads.
Contact and support FAQ
What should I include in a technical support request?
Include the affected product area, expected and actual behavior, MQTT client and protocol version, relevant timestamps, and the smallest reproducible sequence. Remove credentials and private payloads.
Where should I report a security concern?
Send sensitive security reports by email rather than opening a public issue. Describe the affected boundary and reproduction steps without including live credentials or customer data.
Can you troubleshoot data sent through the public broker?
The public broker is a shared, best-effort sandbox. We can help with a reproducible client or protocol issue, but sessions, retained state, credentials, and availability are intentionally not guaranteed.
Check the known boundaries
These guides resolve common client, security, and sandbox questions before a support thread is needed.