solderdatabraid29/aegis-vaultgrid

Aegis VaultGrid is a local-first CS2 trading workspace that combines a fee-adjusted spread scanner, account inventory vaults, buy-order planning and fee/endpoint settings. It suits Windows users who want their skin-trading math and vault state kept in local JSON rather than in an account-backed dashboard.

What it does

The scanner compares executable buy and sell opportunities and reports what remains after the sell-side fee instead of a headline spread. Each venue carries its own fee and settlement currency, with Steam Community Market, Buff163, CSFloat, Skinport and Waxpeer given default assumptions; the fee models are editable. A separate buy-orders workspace keeps acquisition limits and bid position visible, and connections and fees store the assumptions behind every estimate. See the workspace overview in the README.

A second function is the account vault: inventories, access details and local Steam Guard codes can be reviewed, and a vault imported for the current session. The Rust side generates the five-character Steam Guard code from a shared secret for a 30-second window, and persists fee models and vault metadata to a local state file in the Tauri app data directory. That makes the vault and TOTP handling a local credential store, not a cloud service.

How to run it

The supported download is a single zip from the latest release containing Main.exe and the runtime; unpacking and launching it needs no installer or admin rights. The README describes Windows 10 and 11 as the target, and says the executable is code-signed. Build-from-source is a separate path: Node.js 20+, stable Rust, Tauri prerequisites, and on Windows WebView2 plus Microsoft C++ Build Tools for packaging, with the order-planner and scanner built as a Tauri v2 app with React 18. The release download and build instructions are the relevant entry points.

Limits to check before relying on it

The UI ships with a deterministic 15-item market fixture, and venue requests sit behind Rust commands described as connectable to authenticated adapters. The README does not document which venues, if any, return live authenticated quotes out of the box, so confirm live data support before treating estimates as market truth. Steam Guard code generation and session-level vault import involve handing real account secrets to a local application; check the source and your own risk tolerance, since the README offers no security audit. The fee defaults and FX assumptions are starting points, not guarantees, and should be reviewed against the venues you actually use.

The project is MIT licensed, so modification and redistribution are permitted under the usual terms.