About
Design got faster. It didn't get better.
Allizai started with a spreadsheet. Two designers and an engineer, tired of reviewing generated screens that all looked the same, began writing down why good interfaces work: one rule per row, each with a source. The spreadsheet became a rule engine. The rule engine became a canvas.
Taste can be taught. So we wrote it down.
01Version history
From a spreadsheet to a canvas.
We ship the company the way we ship the product: in versions, each one a little more opinionated than the last.
5 versions · 3 years
A spreadsheet
400 rows, each a design rule with a source: a paper, a spec, a type manual. Reviewed every Friday, argued about every Monday.
The first rule engine
The rules became code. A linter for design files that flagged contrast, spacing and hierarchy, with the reason next to every warning.
Rules meet a model
A planner proposes, the engine verifies. The day a generated screen passed every rule on the first try, we stopped calling it a linter.
The canvas
No longer a plugin for someone else's tool, but the place the work happens: products, interfaces, slides, ads and websites, on one brand system.
Invite-only, on purpose
A small group of teams who use Allizai every day. We grow slowly so we can listen closely, and the rule count keeps going up.
02What we believe
Four shapes. Four beliefs.
Taste is teachable.
Good design isn't magic. It's decisions with reasons. Write the reasons down and anyone can check them.
Models propose. They don't decide.
Probabilistic where it helps, deterministic where it matters. Same input, same verdict.
Every decision gets a receipt.
If we can't say why a layout looks the way it does, it doesn't ship.
Brands deserve a system.
Not a PDF that nobody opens, but variables and rules that every file obeys.
03The team
Small on purpose. Always in the file.
We keep our names off the website and our work on it.
Designers, engineers and researchers from type foundries, browser teams and design tools, working across three time zones.