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.

Fleet lets IT and security teams query every device in their organization like a SQL database, using osquery to surface installed software, running processes, configurations, and vulnerabilities within seconds across macOS, Windows, Linux, iOS, Android, and ChromeOS. The Go-based server exposes a web console and REST API for centralized device management, with MDM capabilities built on nanoMDM for Apple device enrollment, configuration profiles, and remote lock or wipe. Vulnerability management cross-references installed software inventories against NVD and OVAL CVE databases, automatically flagging known vulnerabilities with severity scores and remediation guidance. Software deployment handles OS updates using Apple Declarative Device Management, Windows Update, and custom installer packages distributed through S3-compatible storage. A GitOps workflow enables infrastructure-as-code management where device policies, osquery queries, and configuration profiles live as YAML files in Git repositories, with CI/CD pipelines pushing changes through the fleetctl CLI. The fleetd agent bundle includes osquery for telemetry, Orbit for version management, and Fleet Desktop providing end users a menu bar status indicator. Integrations connect to Snowflake, Splunk, Elastic, Jira, Zendesk, Vanta, and GitHub Actions for automated compliance reporting. CIS benchmark policies verify security baselines across operating systems. Deployment requires MySQL for persistence and Redis for caching, running as Docker containers or on Kubernetes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Point your RustDesk clients at CortenDesk and the bare open-source server turns into a managed fleet console with a real address book, real access control, and a remote client that lives in the browser. One container runs the ID server, the relay, and the console together, and existing key pairs and device IDs move in unchanged, so migration is a hostname change rather than a rebuild. The fleet view shows live presence, platform, aliases, owners, and last-seen for every machine, organized into folders that double as the unit of access control. People see only their own devices plus the groups granted to them, and the same scoping is enforced in the RustDesk client API, not just the web pages. Policies push client settings over the heartbeat, covering permissions, password rules, and capture behavior, and enforced policies revert local changes automatically. Five audit logs record connections, file transfers, sign-ins, security alarms, and console actions, all filterable and exportable to CSV. When a browser is all you have, the built-in web client views and controls machines with file transfer, clipboard, audio, and multi-monitor switching, no installer required. 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.

Every physical device on your network gets a living digital counterpart in Eclipse Ditto: a Thing whose Features hold its current state, desired state, and properties, readable and writable through APIs even while the device itself is offline. Your application talks to the twin over a REST-like HTTP API for CRUD and search, over WebSocket for real-time bidirectional streams, or over Server-Sent Events for change notifications, and Ditto routes commands down the live channel to the actual device when it is connected. Devices and backends connect through managed Connections to MQTT, AMQP 1.0 and 0.9.1, Apache Kafka, and HTTP endpoints, with payload mapping that translates between device formats and Ditto Protocol JSON. Fine-grained Policies decide per subject and resource who may read a temperature, change a setpoint, or receive an event, including namespace-scoped entries and partial change notifications that only reveal fields a subscriber may see. Search across millions of twins uses an RQL query language with custom MongoDB indexes, and Web of Things integration generates Thing Descriptions scoped to each requester's permissions. The bundled Explorer UI lets operators browse Things, inspect Features, and time-travel a twin's state to any past revision or timestamp to see exactly what changed and when. OpenID Connect and basic authentication protect the gateway, and Prometheus metrics expose live entity counts per namespace. 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.

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.

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.