Can my PC run it?
A Linux desktop app that checks your Steam games against your hardware, and against Linux itself.
rigcheck.gorkemkaryol.dev
Note
v1.1 is out. The app is complete; the game database is still filling in. It's crawled from Steam every 4 hours, about 18,000 store pages a day, most popular games first, and the app gets a new copy once a day. Until a game's page has been read it's known by name only (NOT CHECKED YET), and the app looks it up on Steam when you open it, so you still get a verdict. See the roadmap.
- Reads your Steam library. It finds native,
~/.steamand Flatpak installs and every library folder, including other drives, and skips Proton and the Steam runtimes. Add your own Steam Web API key in Settings and the Library can show every game you own, installed or not. Sort it A–Z or by verdict, with a summary on top: "38 of 42 installed games meet the recommended specs." - Detects your hardware. It reads CPU, RAM, every GPU by its PCI ID, video memory, the Vulkan version and the driver straight from
/proc,/sysandvulkaninfo. Hybrid laptops use the discrete GPU, and it warns if your NVIDIA card runs onnouveau. - Gives every game a verdict. It compares your PC with the game's minimum and recommended specs, names the part holding you back, and takes Linux into account: ProtonDB ratings, anti-cheat that blocks Linux, and the Vulkan version Proton needs.
- Searches all of Steam. The Catalog lists every game, most popular first, and filters it: only games your PC can run, ProtonDB tier, native Linux, Deck Verified, no anti-cheat problems. A game the database hasn't checked yet is looked up on Steam when you open it.
- Lets you ask "what if?" Pick a different GPU or CPU on My Rig and every verdict updates.
- Compares two games. Side by side: their verdicts, each part's minimum and how your PC does against it, and their Linux facts.
- Keeps itself current. The game database updates in the background, and the app tells you when a new version is out.
| Stamp | Meaning |
|---|---|
READY |
Meets the recommended specs |
LOW |
Meets the minimum; at least one part falls short of recommended |
TOO WEAK |
At least one part is below the minimum, and the game page says which |
BLOCKED |
Can't run on Linux whatever the hardware, e.g. anti-cheat that denies Linux |
??? |
Not enough data to say |
NOT CHECKED YET |
Known by name only; opening the game looks it up on Steam |
NO DATA |
Not in the game database at all |
Screenshots from the real app on the real game database, rendered offscreen with its test renderer on a Ryzen 5 7530U laptop with Radeon integrated graphics (app/src/screenshots.rs).
Local-first: no accounts, no telemetry, no servers of our own. Nothing about you or your PC leaves your machine.
The app sends plain, read-only requests to three places (four if you add a Steam key), and nowhere else (ROADMAP §6):
| Where | When | What's sent |
|---|---|---|
github.com (Releases) |
At start: is there a newer game database, or a newer rigcheck? Downloads the database when there is | Nothing but the file request |
store.steampowered.com |
When you open a game the database hasn't checked yet | That game's app ID |
shared.akamai.steamstatic.com |
Cover art Steam hasn't cached on your disk | The game's app ID |
api.steampowered.com |
Only if you add your own Steam Web API key: at start and on Refresh, to list the games you own | Your key and SteamID |
Settings → Privacy turns the start-up checks off (then they run only when you ask), and lists the same three places. A build rule (deny.toml) keeps HTTP clients out of every crate except crates/net, which refuses any other host.
Each release has an AppImage (any distro), a .deb (Debian, Ubuntu, Mint), an .rpm (Fedora, openSUSE) and a tarball. AUR packages (rigcheck-bin for releases, rigcheck-git for the latest master) and a Flathub listing are on the way; their recipes are in packaging/.
Install vulkan-tools as well, so rigcheck can read your GPU's Vulkan version and video memory.
Arch is shown; any distro with rustup works. No GUI packages are needed to build, since iced loads Wayland, X11 and Vulkan at runtime.
sudo pacman -S --needed rustup base-devel
rustup default stable # includes clippy and rustfmt
git clone https://github.com/Glory42/rigcheck && cd rigcheck
cargo run -p rigcheck --releaseAll Rust: a Cargo workspace with the desktop app (built with iced), the data pipeline and shared crates. The code is built test-first.
app/ desktop app: Library, Catalog, game page, My Rig, Settings, About (binary: rigcheck)
i18n/ translations (Fluent): en, tr, de
crates/
core/ requirement parser, hardware table matching, matcher (no I/O)
hardware/ Linux hardware detection
steam/ Steam installs, libraries and cover art
gamedb/ games.db and fetched.db (SQLite): schema, queries, verdicts, safe install
net/ the only crate allowed an HTTP client; refuses hosts off its allowlist
pipeline/ data pipeline that builds games.db daily (GitHub Actions)
packaging/ desktop file, AppStream metainfo, AppImage/deb/rpm, AUR and Flatpak recipes
data/ hardware table, seed games, test fixtures
assets/ the pixel-art icon and the scripts that draw it; screenshots
website/ the showcase site (Astro, its own npm project; see website/README.md)
cargo install cargo-deny --locked
cargo test --workspace # all tests; UI tests run headless
cargo clippy --workspace --all-targets -- -D warnings
cargo fmt --all
cargo deny check advisories bans # known vulnerabilities; only crates/net may use HTTP
INSTA_UPDATE=always cargo test -p rigcheck-core --test parser # accept parser snapshot changes, then review the diffCI runs fmt, clippy, tests and cargo deny on pushes to master and on pull requests; pull requests that only touch website/ skip the Rust steps. Other workflows build the game database (build-db.yml: crawls every 4 hours, publishes daily), the release packages (release-app.yml), the Flatpak (flatpak.yml) and the site (website.yml). Screenshots are rendered by an ignored test: RIGCHECK_SCREENSHOT_DB=<a games.db> cargo test -p rigcheck screenshots -- --ignored.
Wrong verdicts, missing hardware, translations and captures of your machine all help. CONTRIBUTING.md explains each, plus how code gets written here (test-first). Please follow the Code of Conduct, and report security problems privately as described in SECURITY.md.
- Game data comes from Steam's store pages; Proton compatibility from ProtonDB reports (ODbL), rated by rigcheck's own rule (ROADMAP §9); anti-cheat status from AreWeAntiCheatYet (MIT); Steam Deck status from Steam's Deck compatibility reports.
- Requirement text in
data/fixtures/requirements/comes from Steam's store pages, for testing the parser. - Hardware scores in
data/hardware.tomlare rough hand estimates. The published database fills in parts the table lacks from Blender Open Data (CC0), and GPU PCI IDs come from pci.ids. - The pixel-art icon is original, drawn by scripts in
assets/brand/.
Code: MIT. The published game database (games.db) includes ProtonDB data, so it's under the ODbL.






