# 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.

Repository: https://github.com/mqttsnet/thinglinks
Canonical: https://ross.abutalabs.com/products/thinglinks
Homepage: https://mqttsnet.com
Language: PLpgSQL
License: NOASSERTION
License Family: other
Topics: mqtt, iot, bifromq, mqtt-broker, rule-engine, spring-cloud, thinglinks, mqttsnet
Last push: 2026-08-13T09:56:35+00:00

## Health v2 (maintenance only)
Score: 88/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 97, release rhythm 70, longevity 100
- inputs: {"age_days": 1811, "days_push": 20, "days_rel": 42, "gap_med": 116, "n_releases_24m": 2}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1070, forks 231 (observed 2026-08-28T04:03:27.945576+00:00)

## What it is
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
- artifact type: application
- maturity: active
- function: iot, message-queue, workflow-automation, monitoring, alerting, data-visualization, self-hosted, web-framework
- domain: iot, self-hosted, microservices, analytics
- platform: jvm, self-hosted, cross-platform
- tags: mqtt-broker, rule-engine, multi-tenant, saas, device-management, modbus, coap, spring-cloud, bifromq, scada, automation, docker, web-server

## Member repositories
- mqttsnet/thinglinks (main) score 88

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:27.945576+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:54:05.161360+00:00, confidence not recorded.
  - readme: https://github.com/mqttsnet/thinglinks (fetched 2026-08-28T04:03:27.945576+00:00, sha 9ae0626edce2)
  - homepage: https://mqttsnet.com (fetched 2026-08-29T12:56:18.324179+00:00, sha 313ff99927e4)
  - site_page: https://mqttsnet.com/about (fetched 2026-08-29T12:56:18.327162+00:00, sha 898c412e167a)
- Data as of 2026-08-30T08:39:29.467469+00:00.