TeslaMate
Logging every drive, charge, and idle stretch of a Tesla to a database you own, TeslaMate shows where the battery went, including degradation, vampire drain, and charging cost. Battery health comes first: the dashboard estimates usable capacity, range lost, and degradation against mileage. Idle losses come next, with Vampire Drain listing how much charge disappears during every idle period and a States view recording every online, asleep, and offline stretch. The car is left alone to fall asleep, so logging adds no extra vampire drain. Charging sessions show curves, energy added and used, efficiency, and cost, using per-location prices attached to geo-fences drawn on a map. Each drive records second-by-second speed, power, elevation, and temperature, plotted on a route map beside tire pressure and consumption charts. Trip, Drives, Efficiency, Drive Stats, Mileage, Updates, Statistics, and a lifetime driving map fill in the rest. Live vehicle data goes out over MQTT to Home Assistant, Node-RED, and Telegram, and old history imports from TeslaFi or tesla-apiscraper. Several vehicles on one Tesla account work together, addresses are looked up automatically, and the web interface offers light, dark, or system themes in 19 languages. Sign-in uses Tesla access and refresh tokens that TeslaMate encrypts with a key you set. It works best on an always-on server. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Eclipse Kura
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.
EMQX
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.
Tesserae
Built for e-ink screens, Tesserae composes calm wall dashboards from your calendar, weather, and Home Assistant data in a browser, then renders each frame at the panel's exact resolution. Lay out pages as a grid of cells or on a free canvas of widgets, text, and shapes, with a live preview. What you see is what paints. Dozens of bundled widgets cover weather, calendars, clocks, news, to-do lists, and photos, and a community catalog adds more widgets, themes, and templates. Frames are dithered to each panel's measured palette, so photos and gradients stay clean on Spectra 6 color, mono, and grayscale screens. One server drives a whole fleet. Each panel keeps its own dashboards, schedules, and rotations, and smart sync renders just before a battery panel wakes while quiet hours let it sleep overnight. Seeed reTerminal and XIAO panels flash from the browser, and Pimoroni Inky, Waveshare, M5Stack, TRMNL-compatible devices, and KOReader Kindles and Kobos work too. Inside Home Assistant it runs as a sidebar App. Home Assistant widgets show entities, history, energy, and cameras, and MQTT discovery turns each panel into a device with its frame, battery level, and signal. No account is needed, and update checks stay off unless you opt in. Ask Claude or any MCP client to lay out a dashboard, check a preview, and push it. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
ejabberd
A single ejabberd node carries chat, device telemetry, voice calls, and federated messaging at once, because the same Erlang server speaks XMPP, MQTT, SIP, and Matrix over one authentication, storage, and clustering layer. Users get standards-based instant messaging with group chats, message archives, publish-subscribe, message carbons, push notifications, and OMEMO encryption, and your server federates with the global XMPP network out of the box. Devices publish and subscribe through the built-in MQTT broker on TCP or WebSocket transports, sharing accounts and access rules with your chat users instead of needing a second broker. Voice and video calls route through the integrated SIP gateway and STUN/TURN support, so WebRTC clients get signalling and media relay from the same deployment. Matrix support bridges federated rooms into the same infrastructure, letting two decentralised ecosystems interoperate without a separate bridge stack to babysit. Clustering with consistent hashing scales a deployment across nodes, and a single node is rated at two million concurrent sessions for very large communities. Operators manage everything from the web admin and command line, with SQL or Mnesia storage, LDAP authentication, and virtual hosting for multiple domains on one server. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.0 licensed.
Zigbee2MQTT
Zigbee2MQTT bridges a Zigbee smart home network to MQTT so bulbs, switches, sensors, and locks from hundreds of vendors work with your own automation server instead of each manufacturer's cloud bridge. It supports 5,798 devices from 608 vendors, so a Philips Hue bulb, an IKEA TRÅDFRI switch, an Aqara sensor, and a Tuya plug can all join one coordinator and speak one protocol. The built-in frontend on port 8080 shows every paired device with its link quality, battery level, and live state, and lets you rename, reconfigure, bind, or remove devices without editing YAML. A network map view charts which routers carry traffic for which end devices, making weak spots and dead zones visible before automations start failing. Groups collect devices that should act together, scenes capture lighting states for a room, and bindings let a switch talk directly to a bulb even when the server is briefly offline. Firmware stays current through over the air updates you can trigger or schedule per device from MQTT topics or the frontend, including downgrades when a new release misbehaves. Home Assistant picks everything up automatically through MQTT discovery, while openHAB, Domoticz, and Node-RED flows subscribe to the same plain JSON topics. The coordinator plugs into the host by USB or joins over the local network, while the bridge, frontend, and broker traffic run headlessly beside Mosquitto or EMQX. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.
Magistrala
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.
Eclipse Hono
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.