Gaseous vs ROM Manager

Gaseous Server is a free, open-source self-hosted server for managing ROMs and game titles with basic in-browser emulation. It uses multiple sources to identify games and provide metadata. ROM management supports platforms listed by IGDB, while the built-in emulator covers a documented subset including Game Boy, Nintendo 64, PlayStation, Sega Saturn, and Super Nintendo. Installation options include Docker, source, Unraid, and a Windows MSI package. Windows installation is described as experimental. Setup requires MariaDB 11.1.2 or MySQL Server 8+ and FFmpeg; an IGDB API key is optional when using the Hasheous proxy. From version 2.0, authentication includes passwords, two-factor authentication, and OAuth2/OIDC, with Google, Microsoft, and custom OIDC providers documented. The project uses the AGPL-3.0 license and links to Discord for community support. Maintainers recommend avoiding internet exposure when remote access is unnecessary and state that exposure is at the user’s own risk. The free plan is a self-hosted server, so the operator supplies the database and FFmpeg.

ROM Manager is free, MIT-licensed software for organizing and converting retro console game ROMs. Its pipeline extracts archives, renames files using known game codes, converts ISO or WBFS images to CHD or RVZ, and cleans up files. It can create missing cue sheets for BIN tracks. Interfaces include a command-line tool, Python API facade, MCP server, and optional agent server with an AG-UI web interface. CLI and MCP tools can manage a self-hosted RomM library through its REST API using Basic or OAuth2 authentication. MCP tools cover conversion, game-code lookup and naming, and RomM resource groups, with environment toggles controlling domains. The server supports stdio, Streamable HTTP, and SSE transports; authentication is configurable, with none as the local default. Local conversion needs no service URL or credentials, while RomM access requires server details and credentials or a token. Conversion depends on external chdman and dolphin-tool binaries; extraction uses 7z or optional backends. Destructive cleanup can remove source files, so backups are advised.