Zipix · Founder & Technical Director
Zipix
A mobile micro-game studio, built solo.
Building the studio for a team.
Scroll
The bet

A whole game in about a minute.

Mobile-first micro-games, each one complete in about a minute, with a clean win or loss and an honest timer. Small enough to finish in one sitting, with nothing padded to keep you longer.

Ten weeks, solo

Seed to live.

Designed, built, and shipped end to end, before hiring anyone.

0
Games shipped, one shared engine contract
0
Weeks from seed to live in production
0
Automated tests across the platform
In production across web and native. TypeScript, Phaser 3, Capacitor, Cloudflare, Supabase.
20
Live games
Twenty games, one engine contract.
A shared host runtime every game plugs into, so a new game is just content on top of it. Design tokens carry the brand from the web shell onto the game canvas.
The machine

The studio is a system a team plugs into.

CLI control plane
One entry point for every privileged operation, secrets injected, no loose scripts.
Shared design tokens
One semantic system across the web UI and the game canvas.
Automated test gates
437 tests standing between a change and production.
Release engineering
Nine CI/CD pipelines, versioned and repeatable.
AI-driven development

One operator, the output of a team.

19 agent playbooks
Each discipline's workflow, codified once and reused.
Game-creation pipeline
Scaffolds, implements, and verifies a game, with a human checkpoint at every stage.
The lean-ops case study goes deep on this. Read it →
Live operations

Every change has a tested path back.

Release manifest
Every prod-bound change captures its steps and its smoke check.
Kill switches
Turn a feature off without shipping a deploy.
Incident & cost runbooks
The next step is written down before it's needed.
Production monitor
Degradation pages me, not the players.
What's next

Built for a team to plug into.

The system is live and the seat is open. I'm ready for the team it was built for.