Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
upstream: github.com/home-assistant/core (opens in new tab) · github.com/openhab/openhab-distro (opens in new tab)
Pick Home Assistant
If you want the large integration catalogue and a UI automation editor that needs no code, and can live without apps on a Container install.
Pick openHAB
If you prefer its Things, Channels and Items model, want rules as text files or Blockly, and are fine hosting a Java platform that idled at about 170 MB more RAM than Home Assistant in our check but used less than half the disk.
Home Assistant and openHAB are the two long-running open-source hubs in the Home automation category, and they answer the same question from different directions. Home Assistant's README says it is "open source home automation that puts local control and privacy first", a Python project "Powered by a worldwide community of tinkerers and DIY enthusiasts". openHAB calls itself "an open source, technology agnostic home automation platform which runs as the center of your smart home!", a Java platform built on OSGi. Both run on your own hardware without a vendor cloud. The differences are in how you configure them, how you install them, and how much JVM you are willing to host.
Home Assistant is built around integrations. The README describes a "modular approach so support for other devices or actions can be implemented easily", and its repository lists "Featured integrations" that link to the project's integration catalogue. The README says it is "perfect to run on a Raspberry Pi or a local server", and the install page recommends Home Assistant OS, "an embedded, minimalistic operating system", for most users.
openHAB is built around a small set of concepts. The docs say "Bindings are software packages that are installed by the user in openHAB" and translate commands in both directions between your device and a Thing. "Channels are the logical link between a Thing and an Item", and Items are "the openHAB (software) generated representation of information about the devices". The distribution README says it is "designed to be vendor-neutral as well as hardware/protocol-agnostic" and "a pure Java solution, fully based on OSGi". If you like a clean model of devices, channels and logic kept separate, that vocabulary is the point of the project.
In Home Assistant you build automations in an editor by choosing from your devices and entities, and upstream says "No coding is required." YAML is there for what the editor does not offer: the automation docs point to "the options that are only available in YAML". An automation is triggers, conditions and actions, plus flow-control steps "such as waiting, choosing, and repeating". One detail from the docs worth knowing early: an automation starts "when something happens, not while something is true".
openHAB gives you more than one way to write rules. "Rules are placed in the folder $OPENHAB_CONF/rules", and "Rules can be created and edited with in the UI" as well. The Rules DSL is a text language whose "syntax is very similar to Java", built on Xtend; Blockly is "a visual way of programming openHAB rules, which may be more suitable for beginners"; and the docs link a separate page for JSR223 scripting. Text files that live in a conf folder suit people who keep their setup in version control. The cost is that you choose among languages.
Our Home Assistant page uses the Container install: the official compose file with ghcr.io/home-assistant/home-assistant:stable, privileged: true and network_mode: host, with config in ./config. That choice has a cost the install page states plainly: "Home Assistant Container installations don't have access to" apps, and because integrations "such as Thread and Z-Wave" are "controlled by apps", "There is no out-of-the-box support for these on Container installations." The upstream docs say Container means you supply your own system with container orchestration and handle updates manually. Home Assistant OS is the type that supports apps, and it takes over the machine, which is why a general-purpose VPS is the Container case.
openHAB's snippet in our catalog pins openhab/openhab:5.2.3, runs one container, and keeps its state in three named volumes: conf, userdata and addons. The Docker docs recommend host networking because "openHAB requires UPnP discovery so this parameter makes the Docker container use the host's network stack"; the docs add that UPnP relies on IP multicast, "limited to a local subnet". Our snippet publishes port 8080 instead of using host networking, so it gives you the web UI, not automatic discovery on a LAN. USB radios are the other Docker caveat: the openHAB docs say such devices "will not be available by default to the dockerized system" and suggest passing them with devices:, while Home Assistant's official compose file runs with privileged: true, which is how our snippet gives it access to USB Zigbee and Z-Wave sticks.
For a native install, openHAB's install page asks for "the 64-bit version of the Java 21 version of the JVM" and recommends a dedicated machine "connected by Ethernet and running continuously".
Home Assistant's repository is Apache-2.0. openHAB's distribution repository is EPL-2.0, the Eclipse Public License 2.0. Both are open-source licences, and neither project's catalog entry lists a paid tier, so the licence will rarely decide this one.
The 2 GB on our Home Assistant page and the 1 GB on our openHAB page are our estimates for a VPS. Home Assistant publishes no server RAM minimum; its nearest figure is for Raspberry Pi, a Pi 4 or 5 with "minimum 2 GB RAM". openHAB's openHABian docs say any old x86 machine will do and "all you will need is 1 GB of free RAM", and for a Raspberry Pi, "Ensure your RPi has a minimum of 2 GB."
What we measured, on a GCP e2-standard-2 test box running Ubuntu 26.04 with Docker, is idle at first boot with each default install snippet and nothing paired to it. Home Assistant idled at ~340 MB of RAM and ~3.3 GB of disk (September 2026). openHAB idled at ~512 MB of RAM and ~1.4 GB of disk (October 2026). Those are a floor for a fresh hub, not a figure for a house full of bindings, history and add-ons, and they do not rank the two by load: the JVM-based openHAB used more memory at idle in our check, Home Assistant's image used more disk.
Choose Home Assistant if you want the large integration catalogue, a UI editor that needs no code, YAML for the rest, and you accept that the Container install on a VPS leaves out apps. Expect to run it with host networking and privileged access, as the official compose file does.
Choose openHAB if you like its Things, Channels and Items model, want rules as text files or Blockly, and are comfortable with a Java platform whose Docker docs ask you to think about volumes, user IDs and network mode. It idled at about 170 MB more RAM than Home Assistant in our check and used less than half the disk.
If you have neither a hub nor strong opinions, start with whichever vocabulary you can read after five minutes of the docs: automations built from entities, or bindings feeding Items. We rate Home Assistant 3 out of 5 for difficulty and openHAB 2 out of 5.
Both installs are verified on Ubuntu 26.04: the compose file for Home Assistant and the pinned compose file for openHAB. Home Assistant answers on port 8123 and openHAB's snippet on 8080; both are plain HTTP, so put a TLS reverse proxy in front before exposing either to the internet, and keep them behind authentication since both control physical devices. A VPS cannot see your home LAN, so local discovery will not work from the cloud: devices there need a VPN or a bridge to the server, and many people instead run the hub on a box at home.
No. Home Assistant is Apache-2.0, openHAB is EPL-2.0.
Home Assistant if you want the large integration catalogue and a no-code automation editor, accepting that a Container install has no apps. openHAB if you like its Things, Channels and Items model and rules as text files or Blockly, and are comfortable with a Java platform. Both are verified on Ubuntu 26.04 as a single container.
Yes, as Home Assistant Container, which is what our install snippet uses. The install page says Container installs "don't have access to" apps, and that integrations such as Thread and Z-Wave are controlled by apps, with "no out-of-the-box support for these on Container installations". Home Assistant OS is the type that supports apps. Our measured idle figure for the Container install is ~340 MB of RAM.
A native install does: the install page asks for "the 64-bit version of the Java 21 version of the JVM". Our catalog snippet runs the openhab/openhab Docker image instead, pinned to a stable release, with conf, userdata and addons volumes. It idled at ~512 MB of RAM on our test box.
Our 2 GB (Home Assistant) and 1 GB (openHAB) floors are estimates. Home Assistant publishes no server minimum; for a Raspberry Pi 4 or 5 it asks for at least 2 GB. openHAB's openHABian docs say an x86 machine needs 1 GB of free RAM and a Raspberry Pi a minimum of 2 GB. On our GCP e2-standard-2 box, idle at first boot, Home Assistant used ~340 MB and openHAB ~512 MB.
Paid link — we earn a commission if you shop through it.
A whiteboard-and-docs workspace on a plain Compose file vs. native apps on a commercial server.
A full identity platform vs. a passkey-only sign-in box.
Two modern IdPs, built for different jobs.