OpenRemote is an IoT platform that models every building, EV charger, solar panel, and street light as an asset in one tree, then maps, charts, and automates them from a single web dashboard. Define your own asset types, and give each attribute live readings, writable setpoints, history, and forecasts. Connect hardware with protocol agents for HTTP, MQTT, Modbus, KNX, Z-Wave, LoRaWAN, SNMP, and serial, discovering devices or importing project files where the protocol allows. Plot assets on a map with live position and heading, tint markers by attribute value, and add geofences and GeoJSON layers. Automate with When-Then rules, a drag-and-drop Flow editor, or Groovy and JavaScript rules, and run them on a schedule. Raise e-mails, push notifications, webhooks, or assignable alarms from the result. Compose shareable dashboards in Insights from nine widget types, including charts, KPIs, gauges, maps, and tables. Give each customer a realm with its own users, roles, and white-label branding. Sync edge gateways to a central instance and open them remotely through tunnels. Let devices with X.509 certificates register themselves. Read and write every attribute over REST, MQTT, or WebSocket, and let AI assistants manage assets in plain language through the MCP server. Typical projects span smart cities, building and energy management, and equipment fleets, in an interface that speaks nine languages. 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.

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.

Kuzzle ships a production-ready backend from day one: data storage with Elasticsearch search, real-time pub/sub notifications, user authentication, role-based permissions, and a multi-protocol API serving HTTP, WebSocket, and MQTT simultaneously on port 7512. Rather than rebuilding these standard features from scratch for each project, you get a ready-made backend that accepts connections from web applications, mobile clients, and IoT devices through one unified API surface. Elasticsearch provides persistent document storage with full-text search, geospatial queries, and aggregation pipelines, while Redis handles internal caching and memory storage operations. The Koncorde real-time engine powers pub/sub messaging and database notifications, enabling clients to subscribe to document changes with filter conditions that trigger instant updates when matching data is created, modified, or deleted. User management includes JWT-based authentication, role-based access control with granular permissions at the controller and action level, and pluggable authentication strategies via Passport.js. The extensible plugin framework allows developing custom business logic, additional authentication providers, storage connectors, and protocol handlers. Client SDKs for JavaScript, Dart, Kotlin, and C++ accelerate frontend development, while the Kourou CLI provides command-line API access and project scaffolding. The Vue.js Admin Console offers a web interface for managing indexes, collections, documents, users, profiles, and roles. Horizontal scaling through masterless cluster mode targets 99.99% uptime without single points of failure. 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.

Wire nodes together in a browser, deploy in one click, and real-time data flows from sources through transformations to outputs: Node-RED is the OpenJS Foundation's flow-based programming tool for event-driven applications. Born at IBM as a proof-of-concept for manipulating MQTT topic mappings, it has become the lingua franca of IoT and automation glue - home automation, industrial control, edge data collection - with a community library of over 5,000 contributed nodes and flows covering protocols, devices, and services. Where visual wiring runs out, JavaScript function nodes written in a rich in-editor code editor take over, and every flow serializes to importable, exportable JSON that shares cleanly and version-controls sensibly. Version 5.0 (2026) delivered the largest editor overhaul in the project's history: a rethought layout with Explorer and Information panels in a split sidebar, a native dark theme with theme variants, improved accessibility, and refreshed node appearance. The runtime is lightweight Node.js, exploiting the event-driven non-blocking model so the same flows run on a Raspberry Pi at the network edge or a cloud VM. Apache-2.0 licensed with 240+ contributors, it pairs naturally with dashboard nodes for live charts and controls.

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.

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.

With over 31,600 GitHub stars and thousands of production deployments, InfluxDB 3 Core is the open-source time series database rebuilt in Rust on the FDAP stack — Apache Flight for high-throughput data transfer, DataFusion for vectorized SQL query execution, Arrow for columnar in-memory representation, and Parquet for compressed columnar storage. The engine delivers sub-10ms query response times on recent data and handles millions of writes per second through line protocol ingestion over HTTP, with unlimited tag cardinality eliminating the high-cardinality limitations that plagued earlier InfluxDB versions. The diskless architecture persists data as compressed Parquet files to S3-compatible object storage, Azure Blob, Google Cloud Storage, or local disk with configurable partitioning strategies, while the write-ahead log and in-memory buffer serve real-time queries against recent data before compaction. Native SQL support through DataFusion includes window functions, CTEs, subqueries, and joins, while InfluxQL maintains backward compatibility with existing InfluxDB 1.x and 2.x applications through the same query API. The embedded Python VM enables processing engine plugins and triggers that execute custom logic on write events, perform cross-database queries, and transform data in real time without external tooling. Flight SQL clients provide high-performance query access from Python, Go, Java, and Rust, and the HTTP API supports writes in line protocol format compatible with Telegraf's 300+ input plugins. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT/Apache 2.0 dual-licensed.

Whether it is a delivery van, a trailer in a storage yard, or a dog on a hike, Traccar is the GPS tracking server that puts it on one live map you host and control. Every position and event lands in your own SQL database. Over 200 protocols covering 2000+ tracker models decode out of the box, so a Teltonika fleet unit and a budget dongle share one device list. Pick a device to see speed, address, ignition, and total distance. Routes replay on a timeline slider, and a ruler tool measures distances. Geofences can be polygons, polylines, or circles, linked to devices or groups, colored as you like, and limited by calendar schedules. Alerts for overspeed, fuel drops, offline devices, alarms, and maintenance arrive by web, email, push, SMS, Telegram, or WhatsApp. Reports cover trips, stops, summaries, charts, events, and positions, with Excel export and scheduled email delivery. Commands go out over the tracker's own connection or by SMS, queued for offline devices. Computed attributes derive ignition or fuel values from raw inputs using expressions. Resellers get admin, manager, user, and read-only roles with device limits, plus white-label branding. Traccar Client lets a smartphone report as a tracker, and Traccar Manager monitors devices from mobile. Teams who want AI assistants to query their devices can add the MCP endpoint, which is optional. 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.

Your house already has lights, locks, sensors, thermostats, and speakers from many brands, and Home Assistant gives them one local control room with no vendor cloud in the loop. To close the shutters when the outdoor temperature holds above 25 °C, or to be alerted when the garage door is left open, build the routine in the visual editor: When, And if, Then do. Scenes, scripts, and blueprints package it for reuse, and run traces show what it did. More than 1,500 integrations cover Zigbee, Z-Wave, Matter, Thread, MQTT, ESPHome, Bluetooth, Hue, and Sonos, and network discovery offers known devices for one-step setup. To see the house at a glance, drag tile, thermostat, gauge, graph, and map cards into a dashboard, then put it on a TV with Home Assistant Cast. The Energy dashboard answers where the power goes, drawing solar, grid, battery, gas, and water as one distribution diagram with cost totals and per-appliance tracking. To talk to the house, use Assist: natural-language commands, wake words, and custom sentences run locally or through Home Assistant Cloud. The map panel shows who is home, plotting people against zones such as Home, Work, and School from the iOS and Android companion apps. Areas and labels keep large setups tidy, and multi-factor authentication guards each account. 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.

Over 400 technologies and thousands of smart devices from any manufacturer, unified under one roof: openHAB is the vendor-neutral home automation platform with a pluggable binding architecture. Each binding translates a device or service into openHAB's clean abstraction: Things expose Channels, Channels link to Items, and Items feed a rules engine that runs your home. That engine meets you at your skill level: Blockly gives non-programmers drag-and-drop visual logic, JS Scripting (GraalJS with the openhab-js library) is the modern text-based standard, the classic Rules DSL remains supported, and JSR223 opens the door to Python, Ruby, and Groovy. Time- and event-based triggers, scripts, notifications, and voice control compose into automations of any complexity, and users report decade-old rule sets still running rock solid. The Main UI handles configuration, semantic modeling, and now built-in charting - no external Grafana required. Built in Java on Apache Karaf's OSGi runtime and stewarded by the non-profit openHAB Foundation, it requires no cloud to function: everything runs locally, talking directly to your devices. Optional connectors bridge to Alexa, Google Assistant, and HomeKit, with iOS, Android, and web apps for control from anywhere.

Every server, embedded board, and edge gateway you manage becomes reachable through one SSH address in ShellHub, even when it sits behind NAT with no public IP and no open inbound port. A small agent on each device dials out to your server, so a box on a customer LAN or a cellular link needs nothing beyond outbound web access. Connect with the stock ssh client by typing [email protected]@server, or open a terminal in the browser, and scp, sftp, rsync, and port forwarding work unchanged. SSH identities tie every key to a named team member, so removing someone ends their access on every device at once. Default-deny access policies grant or block members, roles, users, or API keys by device tag, Linux login, and source address, and can require a fresh browser confirmation before a session opens. Provisioning keys enroll whole fleets through automatic, manual, webhook, or allowlist acceptance, with usage limits, expiry dates, and tags. The Sessions page records who connected to which device, as which login, and from where, and browser terminals can be recorded and replayed. A Docker connector turns containers into devices that policies can grant one by one. Four member roles shape what each person can change, and the HTTP API, API keys, and an MCP server let scripts and AI assistants list devices and review sessions. 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.

When your community asks what its LoRa mesh is doing right now, PotatoMesh answers with a live map, chat log, and node table built from the traffic your own radios hear. It is a self-hosted dashboard for Meshtastic, Meshcore, and Reticulum networks, with no MQTT clutter. Each node gets a detail page charting battery, voltage, channel utilization, temperature, humidity, and air quality over the past week, plus the neighbors it hears with signal strength and the trace routes it appears in. New nodes and telemetry reports pop up in the chat as they arrive, and a charts page follows telemetry and packets per hour across the whole network. Federation finds other PotatoMesh communities automatically and plots them on a world map with active-node counts per protocol. Ingestors feed the dashboard from radios over serial, TCP, Bluetooth, or passive UDP, and several can report to one instance. Open browsers update live, a Prometheus endpoint exports metrics, and Markdown pages publish your rules, contact details, or legal notice. Add a stop-sign emoji to a node's name to hide it, or switch on private mode to drop the chat entirely. 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.