OpenMQTTGateway vs Home Assistant Companion

A side-by-side comparison of two self-hosted home automation options — licensing, setup difficulty, resource needs, and what each one replaces.

Not the right match-up?
FeatureOpenMQTTGatewayHome Assistant Companion
CategoryHome AutomationHome Automation
LicenseGPL-3.0Apache-2.0
LanguageC++Kotlin
Setup difficultyMediumEasy
Min. RAM64 MB64 MB
Deploymentbare-metal, binarysource
GitHub stars★ 4,073★ 3,788
First released20162020
ReplacesSmartThings HubGoogle Home app

Why pick each one

Choose OpenMQTTGateway if…

  • Released under the GPL-3.0 license
  • Active community (4.1k GitHub stars)
  • Written in C++
  • Tiny footprint — runs in 64 MB RAM
OpenMQTTGateway details

Choose Home Assistant Companion if…

  • Turns phones into sensors
  • Tight HA integration
Home Assistant Companion details

Frequently asked questions

Is OpenMQTTGateway or Home Assistant Companion better?

Neither is universally better. OpenMQTTGateway has the larger community, while Home Assistant Companion is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.

Are OpenMQTTGateway and Home Assistant Companion free and open-source?

Yes. OpenMQTTGateway is licensed under GPL-3.0 and Home Assistant Companion under Apache-2.0. Both can be self-hosted at no software cost.

Can I run OpenMQTTGateway and Home Assistant Companion with Docker?

OpenMQTTGateway: check the project docs for container support. Home Assistant Companion: check the project docs for container support.

Related comparisons