Garlic-Hub

Digital signage device and content management system with SMIL playlist support and scheduling.

Steady · 63
63/100
Steady

Maintained, but at a slower pace than the leaders in its category.

Maintenance 21/40
Releases 25/25
Community 2/20
Momentum 15/15

Commit activity more than 52% of tracked projects; popularity more than 9%. How this is calculated.

Commits, last 11 months

2025-12: 0 commits 2026-01: 0 commits 2026-02: 0 commits 2026-03: 0 commits 2026-04: 0 commits 2026-05: 0 commits 2026-06: 61 commits 2026-07: 16 commits 2026-08: 10 commits 2026-09: 14 commits 2026-10: 247 commits
2025-12 348 total 2026-10
Stars151
Latest releasev1.2.0 · 2 Nov 2026
Repo updated15 Nov 2026
LicenceAGPL-3.0
Built withDocker

Is Garlic-Hub actively maintained?

Development is ongoing. The repository recorded 348 commits over the same window, and the last three months alone account for 271 of them.

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

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

Garlic-Hub ranks #31 of 77 in Miscellaneous, placing it mid-table for maintenance activity.

What Garlic-Hub actually does

Garlic-Hub is a self-hosted digital signage platform used to manage screens and content centrally. It supports standard SMIL playlists and built-in scheduling to control what media appears on remote displays. You can deploy it to coordinate various types of signage hardware from a single web interface.

Best fit: It suits teams or individuals who need an open-source tool to schedule and push media playlists to digital displays across a local network or the internet.

Worth knowing: With a moderate level of project activity and a niche focus, you may encounter edge cases or lack community documentation when troubleshooting hardware compatibility. The AGPL-3.0 licence also means you must release your modified source code if you offer it as a hosted service to third parties.

Deployment notes

Because it is distributed as a Docker container, you will typically need to configure persistent volumes for media and configuration data, alongside a reverse proxy to handle TLS termination.


Alternatives to Garlic-Hub

Projects in the same categories, ordered by health score.