Two players or a full table
Choose two to eight players and a seating layout. Set the first player and turn direction before the game starts.
THE FIELD GUIDE
From the first draw
to the next rematch.
A closer look at what Commander Pod, the Linux app behind Commander Stats, keeps track of—and how it fits into your game night.
Try the interactive demo ↗01 / THE DETAILS
A table that fits your pod.
Start with the people you actually play with. Save their profiles and decks once, then bring the group back together next game night.
Commanders, partners, and borrowed decks
Pick a saved commander or partner pair for each seat. When someone borrows a deck, results belong to the person piloting it.
Made for a shared screen
Large controls face each player around the table. Player photos and commander art make it easy to find your seat at a glance.
02 / THE DETAILS
Keep the game moving.
Life totals are only the start. Keep the counters, turn order, and game clock in one place so the table can focus on playing.
Life, poison, and commander damage
Adjust life and poison, then track damage from individual commanders. Partner commanders have separate damage totals, so their damage stays distinguishable.
Time at the table
Track turns and play duration. Pause for a break, then resume when the pod is ready. Saved play time is separate from the start and end timestamps.
An undo for the accidental tap
Review recent actions in the game menu and undo mistakes. A touch guide is available during play, and opening it pauses the timers.
Finish it, then run it back
Record the result, return to your history, or start another game with the same pod. Save and return home when you need to stop mid-game.
03 / THE DETAILS
Give the bragging rights some context.
A win total tells one story. Participation, commander choice, and shared games tell the rest. Explore the record from more than one angle.
Player, commander, or the combination
Explore wins by player, commander configuration, or pilot plus commander. Partner pairs are treated as a configuration, and rates show decided-game counts alongside them.
Rivalries with receipts
Compare players who actually shared a game. Wins by other players and unresolved games stay separate, rather than becoming an invented head-to-head loss.
Small samples stay visible
Records with fewer than five decided games are marked as small samples. Minimum-games filters help keep one lucky night from looking like a trend.
Go all the way to the source
Search tables and charts, explore commander-hate events, and inspect game and appearance ledgers under All data. Filter history by participants or either partner commander.
04 / THE DETAILS
A better starting point for Rule 0.
Bring some context to the power-level conversation. Deck analysis gives your pod something concrete to discuss before shuffling up.
Your commander collection
Search cards with Scryfall, choose printings and art, and save partner configurations. Online card searches and fresh art downloads require a connection.
Link a Moxfield deck
Associate a decklist with a commander configuration and inspect its analysis. Borrowed-deck scores follow the lender’s exact commander or partner configuration.
Salt and brackets are different signals
Explore salt scores and local bracket estimates separately. These are conversation aids, not an official bracket ruling or a guarantee of how a deck will play.
Look at the assumptions
Inspect score breakdowns and setup uncertainty. Unknown combo prerequisites cannot establish an early combo; starting mana and total setup cost are not interchangeable.
05 / THE DETAILS
Game night should leave a record.
The native app keeps your data locally. You don’t need to create an account to start building a history with your pod.
Recovery while you play
Game actions save as they happen, with running timers checkpointed every five seconds. Recovered games resume paused so you can get everyone settled first.
Backup and restore
Create backups and review a restore before replacing data. The app creates a safety backup before a restore, giving you a way back.
Correct the result, keep the trail
Review history corrections before applying them. Previous records are retained for audit, so changes do not silently rewrite your table’s story.
What you can try here.
The browser demo runs the actual Iced application with sample players, cards, a saved game, and history. Explore the real game controls, setup, deck list, stats, and result corrections. Browser data resets on reload; live services and file import/export are limited to the Linux app.
Take a seat ↗View the Linux app source ↗