Steam Runtime Container Hierarchy
The Steam Linux Runtime container gives Proton a predictable runtime and keeps games aligned with the libraries Proton was built and tested against.
Open Wine Components
Linux game compatibility tooling built around Proton.
Open Wine Components documents how Proton, the Steam Linux Runtime container, UMU-Launcher, UMU-Database, and UMU-Protonfixes fit together for non-Steam game support across Linux front-ends.
Quick Access
Scan the QR code to open the project page and share the docs from mobile.
How Steam Runs Games On Linux
UMU-Launcher Implementation
UMU-Launcher extends the same containerized model to non-Steam games so front-ends can launch them with Proton in a stable, repeatable environment.
Why The Container Matters
Version Compatibility
Proton is built against a known runtime. If a host system exposes incompatible library versions, Proton can fail or behave inconsistently outside the container.
Cross-Distribution Stability
The runtime container creates a stable target across Linux distributions, which is one of the core requirements for reliable game support.
Use UMU-Launcher For Non-Steam Games
UMU-Launcher can be used for any non-Steam game, even when no game-specific fixes are required. UMU_ID and STORE remain optional.
CLI Example
WINEPREFIX=~/some/prefix/path PROTONPATH=GE-Proton umu-run /path/to/game.exe
GE-Proton And UMU-Proton
- GE-Proton tracks Proton’s bleeding edge branch, adds staging patches, codec improvements, extra game fixes, and UMU-Protonfixes support. View GE-Proton Custom Repository
- UMU-Proton tracks Proton’s stable branch more closely while still adding UMU-Protonfixes support. View UMU-Proton Repository
When using UMU-Launcher, setting PROTONPATH=GE-Proton can download and use the latest GE-Proton build automatically. If omitted, UMU-Proton is used by default.
UMU-Database + UMU-Protonfixes
Common Game Fixes
- Winetricks for required Windows components
- Executable swaps when launchers fail but the game works
- DLL overrides for native Windows libraries
- Save transfers between related titles
Integration Partners
The Unified Database System
All tool developers collaborate on UMU’s shared database and fix system.
Key Features
- Each game requiring fixes gets a unique
UMU_ID - Fixes are stored as Python scripts in UMU-Protonfixes
- Metadata is maintained in UMU-Database
Terms
CLI means Command Line Interface.
GUI means Graphical User Interface.
How It Works Together
1
Identify
The front-end knows the game title, store, or codename supplied by the store API or database.
2
Resolve
The front-end queries UMU-Database using the store, title, or codename and receives the corresponding UMU ID.
3
Launch
The tool passes UMU ID and store to UMU-Launcher, which applies fixes through GE-Proton or UMU-Proton when required.
Database Usage
Search Interface
Use the web search UI for quick manual lookups.
API Endpoints
Fetch entries programmatically from the UMU database service.
https://umu.openwinecomponents.org/umu_api.php?store=SOME-STORE?store=SOME-STORE&codename=SOME-CODENAME-OR-APP-ID?codename=SOME-CODENAME-OR-APP-ID?umu_id=SOME-UMU-ID&store=SOME-STORE-OR-NONE?umu_id=SOME-UMU-ID?title=SOME-GAME-TITLE&store=SOME-STORE?title=SOME-GAME-TITLE