RomM

ROM manager for organizing, enriching, and playing retro games, with support for 400+ platforms.

Thriving · 95
95/100
Thriving

High commit volume, frequent releases and growing activity.

Maintenance 38/40
Releases 25/25
Community 17/20
Momentum 15/15

Commit activity more than 96% of tracked projects; popularity more than 83%. How this is calculated.

Commits, last 11 months

2025-10: 323 commits 2025-11: 347 commits 2025-12: 280 commits 2026-01: 200 commits 2026-02: 153 commits 2026-03: 331 commits 2026-04: 328 commits 2026-05: 468 commits 2026-06: 449 commits 2026-07: 762 commits 2026-08: 503 commits
2025-10 4144 total 2026-08
Stars13k
Latest release5.3.1 · 23 Sept 2026
Repo updated28 Sept 2026
LicenceAGPL-3.0
Built withDocker

Is RomM actively maintained?

Over the last 11 months the project absorbed 4144 commits, of which 1714 arrived in the most recent quarter — roughly 571 commits a month.

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

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

Note that RomM depends on a third-party service to work fully. It is self-hosted, but not self-contained: if that external service changes its terms or disappears, your instance is affected.

Among the 22 games - administrative utilities & control panels projects we track, RomM currently has the highest health score.

What RomM actually does

RomM is a self-hosted ROM manager designed to help you organise, enrich, and play retro games across hundreds of different platforms. It acts as a centralised control panel for large collections of game files, streamlining metadata management and browser-based access.

Best fit: It is a good fit for self-hosters with extensive retro game libraries who want a web-accessible interface to catalogue and play titles.

Worth knowing: The software is distributed under the AGPL-3.0 licence, which imposes strict copyleft obligations if you modify and network-host the code. Additionally, relying on browser-based emulation for hundreds of disparate platforms can introduce complex performance and compatibility trade-offs.

Deployment notes

As a containerised application, you will typically need to configure persistent volumes for your game library and metadata storage, along with a reverse proxy to handle TLS termination.


Alternatives to RomM

Projects in the same categories, ordered by health score.