OpenRemote

OpenRemote is a 100% open source Internet of Things (IoT) device management platform aimed at manufacturers, system integrators, and self-hosters.

  • Databases
  • Home Automation
OpenRemote is a 100% open source Internet of Things (IoT) device management platform aimed at manufacturers, system integrators, and self-hosters. It provides device management with auto provisioning, custom asset types, automation through when-then, flow, JavaScript, and Groovy rules, data analytics, and multi-protocol connectivity, surfaced through a white-label web console. It suits self-hosted IoT deployments spanning energy management, industrial IoT, fleet telematics, building management, smart cities, and agriculture.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

73/100 Good

Maintained
100last commit 2 days ago
Popular
672,164 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
2,164
Open issues
500
Last commit
2026-11-19
Latest release
1.34.1
Activity
steady

Checked 3 days ago - source: GitHub (openremote/core)

Resources & Compatibility

Requirements not published yet.

Checked 3 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set up or-setup values before install The or-setup chart creates persistent volumes (OpenRemote’s saved data) and secrets (stored credentials), so review values.yaml, especially basePath, before running it so your data and URLs are written correctly. source
  • Install OpenRemote charts in order For the standard HAProxy path, install the Helm charts in this order: proxy, PostgreSQL, Keycloak, then manager; installing them out of order can leave the app without its database or login service. source
  • Configure Ingress if you use it If you prefer Ingress instead of HAProxy, make sure Ingress is configured and enabled for the Keycloak and manager pods; otherwise you may not be able to reach the login or main manager page. source

Fetched 3 days ago - each note links to its source

Alternatives (6)

Checked 3 days ago - source: AlternativeTo

Common questions

In what order should OpenRemote Kubernetes Helm charts be installed for the standard HAProxy path?

Install the proxy, PostgreSQL, Keycloak, and manager charts in that order; out-of-order installation can leave the app without its database or login service.

What values.yaml setting should be checked before running the or-setup chart?

Review values.yaml, especially basePath, before running or-setup so the persistent volumes and secrets are created so data and URLs are written correctly.

Can OpenRemote be run without a reverse proxy?

In a test environment, it can be configured to run without a proxy if the normal proxy setup is undesirable.

Where is the starting point for setting up the OpenRemote development environment?

The Developer Guide covers how to set up a development environment.

Answers sourced from github.com, github.com, www.reddit.com

Community

Collected 3 days ago - public community threads