head to head · open source
OpenMQTTGateway vs pyatv
OpenMQTTGateway has 4,117 GitHub stars, 910 forks, 48 open issues and last shipped 17 days ago. pyatv has 1,202 stars, 166 forks, 258 open issues and last shipped 3 months ago. OpenMQTTGateway leads on adoption by 243% (4,117 vs 1,202 stars). OpenMQTTGateway is written in C++ under GPL-3.0; pyatv is written in Python under MIT. OpenMQTTGateway has attracted 22% as many forks as stars, pyatv 14%. OpenMQTTGateway was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (home-automation), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| OpenMQTTGateway | pyatv | |
|---|---|---|
| GitHub stars | ★ 4.1K | ★ 1.2K |
| License | GPL-3.0 | MIT |
| Written in | C++ | Python |
| Last push | 2026-10-19 | 2026-08-14 |
| Forks | ⑂ 910 | ⑂ 166 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick OpenMQTTGateway if
- You weight community size — 4.1K stars and counting
- You want the GPL-3.0 license terms
- Your stack matches C++
- You value the larger contributor base for long-term maintenance
pick pyatv if
- You want the pyatv feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Python
- You evaluated both and pyatv fits your workflow better
About OpenMQTTGateway
OpenMQTTGateway aims to unify various technologies and protocols into a single firmware. This reduces the need for multiple physical bridges and streamlines diverse technologies under the widely used MQTT protocol. Sponsors Documentation The documentation is here New to OpenMQTTGateway? Follow the Getting Started guide to flash a board from your browser and see your first sensor data in about 15 minutes. The reference sheet, with the list of all functions, pinouts is here Upload Upload OpenMQTTGateway directly from the upload page (no additional software required) or build your own configuration with PlatformIO…
read the full OpenMQTTGateway overview →
About pyatv
A client library for Apple TV and AirPlay devices ================================================= This is an asyncio python library for interacting with Apple TV and AirPlay devices. It mainly targets Apple TVs (all generations, including tvOS 15 and later ), but also supports audio streaming via AirPlay to receivers like the HomePod, AirPort Express and third party speakers. It can act as remote control to the Music app/iTunes in macOS. All the documentation you need is available at pyatv.dev . What can it do? Some examples include: Remote control commands Metadata retrieval with push updates Stream files via…
read the full pyatv overview →
More in Miscellaneous
Related comparisons
More Internet of Things (IoT) projects
Compare either of these against the rest of the Internet of Things (IoT) field.
Frequently asked questions
Is OpenMQTTGateway or pyatv more popular?
OpenMQTTGateway has 4,117 GitHub stars and pyatv has 1,202. OpenMQTTGateway has the larger community by that measure.
Are OpenMQTTGateway and pyatv free?
Both are open source. OpenMQTTGateway is licensed under GPL-3.0 and pyatv under MIT. Neither carries a licence fee.
What is the difference between OpenMQTTGateway and pyatv?
OpenMQTTGateway is written in C++ and pyatv in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, OpenMQTTGateway or pyatv?
Choose OpenMQTTGateway if you want the larger community (4,117 stars) or its GPL-3.0 licence terms. Choose pyatv if its feature set, stack or MIT licence fits better. Both are self-hostable.