Gaseous vs OxyROMon

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.

oxyROMon is a free, cross-platform command-line tool for organizing and archiving ROM collections. Written in Rust, it checks files against known-good databases and supports console, computer and arcade systems through Logiqx DAT files. Commands can import, validate, check, convert, export and purge ROMs, as well as create M3U playlists for multi-disc games. It is designed for original and lossless formats; exporting to lossy formats leaves the lossless files untouched. Collections can be sorted by region or in 1G1R mode, while arcade sets can be grouped by BIOS, parent and clone. Settings are stored in SQLite with global options and per-system overrides. The documented database sources include No-Intro and Redump for consoles, and MAME or FBNeo for arcade systems. An optional server provides a GraphQL endpoint and web interface for browsing collections, managing settings, and importing ROMs and DATs. The server defaults to loopback, but URL imports can reach hosts accessible to it, so exposing the server beyond loopback requires care. No-Intro DAT handling checks for updates but does not download the DAT files.