Meet Datum: Code-only Design System
Datum is the next-gen design system - entirely in code. Designers direct the build from the terminal. No Figma or canvas during the build. Built for enterprise-scale, multi-product, multi-brand teams, on best practice from Polaris, Carbon and Material. Products consume it, agents query it over MCP, and every change is checked before it ships.

5 seconds at Datum
How it works
Datum. From Latin: that which is given. A fixed point. A ruler.
Not only a design system. An operating system - built to work with AI agents the way design systems were never designed to.
Every token has a contract. Every component passes a gate. Every output is WCAG-verified, industrially governed, and traceable back to a single source of truth that lives in code - not in a file someone left open.
Datum doesn’t just build. It governs. Feed it a broken product and it builds back with precision: tokens verified, drift corrected, standards enforced. What comes out the other side is production-grade, accessible, and ready to scale.
Built for the new workflow. Custom MCP. Agent-ready tooling. Token architecture that agents can read, write, and reason over. Contracts that don’t live in Figma - they live in the codebase, where they belong.
Documentation lives in Storybook for human and directly in the code for AI agents.
Everything that passes Datum is measured. Everything measured is true.
AI agent
Queries components + tokens, reads code directly
Datum MCP
Builds production UI
Checker
Token verifier
Datum MCP, checker and token verifier are built in-house by Amy Ngo and Nathan, her Tech Lead (Claude Code).

Claude Code
GitHub
Storybook
Shadcn
Tailwind

No Figma/ canvas required
Datum cuts down tokens, cost and time
What would your next UI project cost?
Token & Resource Calculator
Put in your own project, the way your team works today. We calculate what the same project costs with Datum. Every number is yours to change.
Pick a side to see where the money goes.
| With Datum | Saved | |
|---|---|---|
| Design | $26K | — |
| Handoff & tool switching | $1,920 | $4,480 |
| Front-end build | $27K | $12K |
| Visual QA & fix loop | $6,400 | $6,400 |
| Iteration rework | $24K | $42K |
| System upkeep | $8,512 | +$8,512 cost |
| AI tokens | $610 | $365 |
| Design-tool seats | $0 | $585 |
| Total | $94K | $57K |
For illustration only. Every team is different. The defaults are our estimates from building Datum and from typical industry pay, not a quote.
See Datum in real time
And this continues to scale
Built on the system, nothing off system. Every screen goes through two checkers, WCAG 2.2 AA and the token verifier, before it ships.
- WCAG 2.2 AA
- 5,592
contrast checks, every state and variant
- Tokens
- 976
token references, all on the system
- Fails shipped
- 0
contrast, tokens, raw hex
- Colour tokens
- 826
named and governed, one system
- Components
- 35
built and governed in code
- Brands
- 5
from one system, every pairing AA
Luxi Math, a live 3D game, governed end to end: 19 screens audited.
Where Datum stands in October 2026. Every release adds to these numbers.
Want us to run this on your real project or a demo?
DM Amy on LinkedIn
