Ross ROSS = Recommend OSS · open-source software intelligence for agents

mqttsnet/thinglinks

Enterprise-grade IoT platform powered by ThingLinks Engine. Supports MQTT / HTTP / CoAP / TCP / Modbus, rule engine, Visual display screen & multi-tenancy. Millions of connections per node. observed · 2026-08-28

github.com/mqttsnet/thinglinks · homepage · PLpgSQL · NOASSERTION (other) observed · 2026-08-28

Health v2 · maintenance only

88/100

  • Activity 97
  • Release rhythm 70
  • Longevity 100

Flags: no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: 116
  • age_days: 1811
  • days_rel: 42
  • days_push: 20
  • n_releases_24m: 2

Full methodology

Adoption not part of the score

1070 stars · 231 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

ThingLinks is an enterprise-grade, multi-tenant SaaS IoT platform built on Spring Cloud microservices with a Netty/BifroMQ-based engine supporting MQTT, HTTP, CoAP, TCP, UDP, and Modbus. It provides device management, a visual rule engine, alarm center, and SCADA-style visualization dashboards, claiming millions of concurrent device connections per node.

Use cases

  • connect and manage millions of IoT devices over MQTT
  • build a multi-tenant SaaS IoT platform
  • ingest Modbus and CoAP sensor data
  • orchestrate device rules and scene linkage without coding
  • set up device alarms with multi-channel notifications
  • visualize IoT asset data on dashboards
  • self-host a private IoT device management system
  • perform firmware OTA updates for devices

When to choose

  • you need a self-hosted, multi-tenant IoT platform with enterprise features
  • you require multi-protocol device access (MQTT, HTTP, CoAP, TCP, Modbus) in one system
  • you expect very high concurrent device connections per node
  • you want a built-in visual rule engine and alarm center
  • you prefer a Java/Spring Cloud microservices stack

When to avoid

  • you only need a lightweight standalone MQTT broker
  • your stack is Python, Go, or Node.js based
  • you need a fully permissive license without commercial considerations (license is non-standard)
  • you want a small single-binary tool rather than a full microservices deployment
  • you need mature long-term production hardening evidence for a young project

Facets

application · maturity active

iot message-queue workflow-automation monitoring alerting data-visualization self-hosted web-framework iot self-hosted microservices analytics jvm self-hosted cross-platform mqtt-broker rule-engine multi-tenant saas device-management modbus coap spring-cloud bifromq scada automation docker web-server

3 sources

Member repositories

RepositoryRoleHealth v2
mqttsnet/thinglinksmain88

For agents

markdown · JSON · MCP: product_card(name="mqttsnet/thinglinks")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem