Free browser games, baked from scratch. No download, no install, no account needed: click and play.
Both games run on the open web and are free to play. Each has a full guide covering the rules, the controls, and how it was made.
Eight wizards. Short, sharp skirmishes. Last one standing.
A chess auto-battler for eight players. Each round you buy pieces, merge three copies into a stronger one, and place your army. Then you play a short chess opening against one rival before both armies fight it out live, every piece striking along its chess lines.
Play solo against seven bots, or open a room and send friends a five-letter code. They can join without an account.
Combine runes. Forge spells. Survive the dungeon.
A pixel-art roguelite built without a game engine. Pair one of seven delivery runes with one of seven effect runes to make 49 different spells, then fight through ten procedurally generated floors to the Archon waiting at the bottom.
Tame companions, collect cards between fights, and spend your gold on permanent upgrades back at the wizard's house.
Some projects aren't games. These two started as tools I wanted for myself.
A local dashboard for Claude Code token usage and cost. It reads the transcripts Claude Code already keeps on your machine and shows turns, tokens, estimated cost, and live sessions and subagents as they run.
It only reads, and only on localhost: nothing is uploaded, and it never reads message content, just timestamps, token counts, and model names.
Sign in with Steam, or just type in a few games, and SteamMap builds an explorable graph linking your library to other games by developer, publisher, genre, and a vibe score drawn from reviews.
A Wrapped-style stats view shows your most-played genres, what your library is worth, and how your taste compares with other players.
Notes on how the games get made: what worked, what didn't, and the occasional detour. All posts
An open-source web game engine built out of our own games: what's in it, how Churn uses it, why Spellbox keeps its own engine, and the new devlog this post runs on.
How we rebuilt this site's colors and type around one idea: slate, chalk, four accents in three strengths, measured contrast, and the template habits we dropped.
Spellbox has no spell list, just two rows of seven runes. The whole grid, mana as simple addition, status effects, and why the magic system is one table.
Every project, game or tool, goes through the same three steps, over and over, until it's ready to ship.
Every project starts scrappy: test the core mechanic or workflow before committing to it.
Then it's heads-down: hand-rolled code, written so I'll still understand it a year from now.
Released in the open: playable, installable, or forkable as soon as it's ready, and not before.