OpenRemote

IoT Asset management, Flow Rules and WHEN-THEN rules, Data visualization, Edge Gateway.

Healthy · 76
76/100
Healthy

Actively maintained with regular releases.

Maintenance 27/40
Releases 25/25
Community 10/20
Momentum 15/15

Commit activity more than 67% of tracked projects; popularity more than 48%. How this is calculated.

Commits, last 11 months

2025-10: 27 commits 2025-11: 21 commits 2025-12: 32 commits 2026-01: 46 commits 2026-02: 54 commits 2026-03: 39 commits 2026-04: 34 commits 2026-05: 30 commits 2026-06: 100 commits 2026-07: 123 commits 2026-08: 59 commits
2025-10 565 total 2026-08
Stars1.9k
Latest release1.31.0 · 24 Sept 2026
Repo updated24 Sept 2026
LicenceAGPL-3.0
Built withJava

Is OpenRemote actively maintained?

Over the last 11 months the project absorbed 565 commits, of which 282 arrived in the most recent quarter — roughly 94 commits a month.

Activity is accelerating: the last quarter carried 174% more commits than the one before it.

The most recent tagged release, 1.31.0, shipped within the last month — a current, installable version exists today.

OpenRemote ranks #9 of 20 in Internet of Things (IoT), placing it mid-table for maintenance activity.

What OpenRemote actually does

OpenRemote is an open-source Internet of Things platform that provides asset management, edge gateway capabilities, and data visualisation. It includes rule engines using flow-based and conditional logic to automate interactions between connected devices and services. Written in Java and distributed under the AGPL-3.0 licence, it is designed to help you aggregate and control disparate connected hardware.

Best fit: It is a solid fit if you need a self-hosted platform to monitor and control heterogeneous IoT deployments with custom automation rules.

Worth knowing: The AGPL-3.0 licence requires you to release the source code of your modifications if you offer the software as a network service, which may restrict commercial usage. Additionally, setting up complex flow rules and edge gateways typically demands a steep learning curve.

Deployment notes

Because the application is built with Java, you will usually need to allocate sufficient JVM memory and pair it with a persistent storage volume for your device data. It is also standard practice to place the service behind a reverse proxy to handle TLS termination.


OpenRemote as a replacement for


Alternatives to OpenRemote

Projects in the same categories, ordered by health score.