Our take
Activeregular commits and releases- Activity
- 87
- Community
- 83
- Issues
- 59
- Pull requests
- 80
+479 stars in the last 30 days
- Releases more often than 91% of the projects we track
- Merges more pull requests than 88% of the projects we track
- More contributors than 78% of the projects we track
RomM is an actively maintained, feature-rich choice for self-hosting a broad ROM collection, with frequent releases and contributions from a large, not heavily concentrated contributor base.
Good fit if
- You want a self-hosted library manager that also supports browser play through EmulatorJS and RuffleRS.
- You need broad platform coverage, metadata enrichment, or save syncing across devices.
- You can run its Python and Docker-based stack and are comfortable with AGPL-3.0 terms.
Look elsewhere if
- You need a standalone desktop ROM manager rather than a self-hosted application.
- You need a documented test suite as part of your adoption criteria, since the supplied project facts report no tests.
- You cannot meet the Python 3.14-or-later runtime requirement or use Docker Compose.
All health signals
| Last commit | 2026-10-29 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 78 (latest 5.4.1, 2026-10-22) |
| Contributors | 100+ (top contributor: 43% of commits) |
| Issues closed, last 90 days | 13+ (typically closed in 6 days) |
| Pull requests merged, last 90 days | 83 (typically merged in 0 days) |
| Project age | 3 years |
Checked on 2026-10-30 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
14,409Forks
824Change since Nov 17, 2026: +12 stars·+3 forks
Overview
RomM is a self-hosted ROM manager and player for people who want to organize, browse, and play their emulator collection in one place. It supports more than 400 platforms and uses EmulatorJS and RuffleRS for browser-based play, so you can launch supported games without setting up a separate player on each device.
It scans ROM collections and enriches them with metadata and artwork, while keeping saves and states in sync across devices. Self-hosting gives you control over your library, and per-user permissions and OIDC single sign-on support shared setups.
Key Features
- Scan ROM collections and retrieve metadata from services including IGDB, ScreenScraper, LaunchBox, and MobyGames.
- Browse metadata for more than 400 platforms, including support for multi-disk games, DLCs, mods, hacks, and manuals.
- Play supported games in a browser using EmulatorJS and RuffleRS.
- Sync saves and states across devices, with conflict resolution.
- Fetch custom artwork from SteamGridDB and track achievements through RetroAchievements.
- Apply ROM hacks and translations with the built-in patcher.
- Share a library with per-user permissions and OIDC single sign-on.
- Connect official clients for Playnite, Android handhelds, and custom firmware devices.
Use Cases
- A retro-gaming enthusiast can centralize a collection and browse it with enriched game details and artwork.
- A household or gaming group can share one self-hosted library while controlling access by user.
- Someone who plays across devices can sync saves and states instead of manually moving them.
- A handheld owner can use the official Android or custom-firmware clients to access a RomM library on supported devices.
What you need
Detected in the repository
- Python >=3.14 (from pyproject.toml)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- Automated checks on GitHub Actions
License in plain words
AGPL-3.0network copyleft
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license notice
- Share your changes: yes, the full source, also when people only use it over a network (e.g. as a hosted service)
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Follow the Quick Start Guide to install and configure RomM. The repository README has further project details.
Considerations
- The stated runtime requirement is Python 3.14 or later, and Docker and Docker Compose are supported deployment requirements. Check that your environment can meet them before adopting the project.
- The supplied project facts report no tests, so teams that require a reported test suite should assess that gap for their own deployment.
- ROM metadata and artwork enrichment depend on external providers, and browser play uses EmulatorJS or RuffleRS. Confirm that your preferred platforms and workflow are supported.
- RomM is licensed under AGPL-3.0. Review its obligations before incorporating or offering modified versions of the software as a service.
Found this useful?
Share it with someone who would like romm.