On the factory floor, the data already exists; it is just locked inside machines, PLCs, and protocols nobody on the analytics team speaks. StreamPipes unlocks it with guided adapters for OPC UA (including a web-based node browser), MQTT, Kafka, Pulsar, REST services, and industrial controllers, turning each source into a live stream in minutes. Domain experts then drag those streams into the pipeline editor, chain processors and sinks on a canvas, and watch connection validation check schema compatibility as they build, with live preview showing real values before anything is saved. Pipelines filter, enrich, aggregate, and route machine data, raise alerts, and write results to the built-in time-series data lake, where the data explorer charts history and spots trends. Finished pipelines run under an overview that starts, stops, and bulk-manages them, while detail views expose logs, metrics, status, and the pipeline as code. Live dashboards carry the same data to shop-floor screens and operations centers, organized around assets so a line, a cell, or a single machine becomes the navigation unit. Developers extend everything with custom adapters, processors, and sinks built on the Java SDK and deployed as microservices, or drive the platform from Python, Go, and Java clients. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Between the factory floor and the cloud sits a gateway that has to speak Modbus to a PLC, OPC-UA to a machine, and MQTT to your platform, and Eclipse Kura is the framework that runs that gateway as a managed, programmable container. Drivers encapsulate each field protocol and its settings, while Assets model the data channels of attached devices, giving every sensor and controller a uniform mirror that applications can read, write, and publish. Kura Wires turns edge logic into a diagram: drag an asset onto the canvas, wire it through timers, filters, and SQL-based aggregation, and publish the result to the cloud, installing extra components from the Eclipse Kura Marketplace when the palette runs short. Telemetry survives bad networks because the data service stores messages locally and forwards them when the connection returns, with publishing policies abstracting the underlying MQTT transport. Administrators manage the whole gateway from the web console: network interfaces, firewall, installed bundles, snapshots of the full configuration that can be exported and restored, and remote deployment and upgrade of applications through the cloud connection. Hardware services expose serial ports, USB, Bluetooth, GPS position, GPIO, I2C, and a watchdog that resets the system when a critical component stops reporting. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. EPL-2.0 licensed.

Thousands of devices speaking four different protocols is where IoT projects usually dissolve into glue code; Magistrala replaces that tangle with one platform where MQTT, HTTP, WebSocket, and CoAP clients share a single identity, provisioning, and messaging model. You organise work into domains, register clients for devices and applications, and connect them to channels that control who publishes and who subscribes, with fine-grained policies deciding which client may touch which channel. Protocol adapters bridge the transports, so a sensor publishing over MQTT and a dashboard reading over WebSocket meet in the same channel without translators in between. Telemetry lands in TimescaleDB through dedicated writer services and comes back out through reader APIs, while the bundled three-node FluxMQ cluster carries the messaging load with mutual TLS on device connections. The rules engine reacts to incoming messages with conditions and actions, alarms flag the readings that breach them, and reports package fleet data for the people who never open a terminal. A Community web UI covers domains, clients, channels, messages, and rules for day-to-day operation, and everything deploys as one Docker Compose stack with Prometheus metrics and Jaeger tracing already wired in. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

With over 16,500 GitHub stars and a track record powering connected vehicle fleets, smart city sensor networks, and industrial IoT deployments, EMQX is the MQTT messaging platform engineered to handle 100 million concurrent device connections in a single cluster while processing millions of messages per second with sub-millisecond latency. The protocol stack supports MQTT 5.0, 3.1.1, and 3.1 with full QoS 0/1/2 support, shared subscriptions, retained messages, and will messages, plus MQTT over QUIC for faster connection setup, reduced head-of-line blocking, and seamless connection migration on mobile networks. The gateway framework extends connectivity to MQTT-SN, CoAP, LwM2M, STOMP, and ExProto for bridging legacy industrial protocols. The SQL-based rule engine processes and transforms messages in real time with over 50 pre-built integrations including Kafka, PostgreSQL, MySQL, MongoDB, InfluxDB, TimescaleDB, ClickHouse, Redis, AWS Kinesis, GCP Pub/Sub, and Azure Event Hubs. The visual Flow Designer creates data processing pipelines without code. Built on Erlang/OTP with a masterless distributed architecture using Mria for state replication, the cluster separates Core nodes for data consistency and Replicant nodes for client-handling workloads. Authentication supports username/password, JWT, PSK, X.509 certificates, and LDAP with configurable ACL rules. The built-in dashboard provides real-time monitoring of connections, subscriptions, topics, message rates, and cluster health. Deployment runs via Docker, Kubernetes with the EMQX Operator, or native packages. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. BSL 1.1 licensed.

Eclipse Hono is an IoT connectivity platform that sits between device fleets and business applications, accepting connections over MQTT, HTTP, AMQP 1.0, and CoAP adapters and normalizing everything into uniform telemetry and event streams. Devices authenticate against a central registry of tenants and credentials, with X.509 client certificates, pre-shared keys, or automatic provisioning for zero-touch onboarding. Applications consume normalized data from Apache Kafka or an AMQP 1.0 messaging network, choosing per tenant which backbone carries its traffic, and send commands back down to devices through the same platform with delivery feedback. Resource limits cap how much data each tenant's devices may move, keeping one noisy fleet from crowding out the rest, while metrics and tracing follow every message hop. The 2.7 release adds preliminary MQTT 5 support with corrected connect reason codes, message tracing logs, and a hardened JDBC device registry backed by PostgreSQL for production tenant and credential management. Protocol adapters scale horizontally as stateless services, so capacity grows by adding instances behind a load balancer. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. EPL-2.0 licensed.