Your calendar, rewritten every morning so you make fewer decisions
Unrelated domain — listed for teams comparing design-adjacent tooling.
Design tokens that stay honest between Figma and production code
Northlight makes your codebase the source of truth for design tokens and generates the Figma side from it. Colour, type, spacing and motion stay identical across both, and drift becomes a failing CI check instead of a discovery three sprints later.
Tokens live in TypeScript with full type-checking, review and history.
Native Figma variables produced through the API — not a plugin panel bolted on.
A stale consumer fails the build instead of surfacing as a visual bug in QA.
CSS, Tailwind, iOS, Android and JSON from one definition.
Values that vary by theme, platform or density — expressible because they live in code.
Generate alongside your existing library and diff before you cut over.
The tokens are not the hard part. The hard part is that Figma and code are two independent databases with no referential integrity between them, and they diverge the moment anyone is in a hurry.
Northlight fixes the direction of authority. Code is the source of truth. Figma variables are generated from it. Drift is impossible by construction rather than by discipline.
tokens.ts → Northlight build → ├─ CSS custom properties
├─ Tailwind theme
├─ iOS / Android resources
└─ Figma variables (via API)
One definition, five consumers, one CI check that fails the build if any consumer is stale.
Generating code from Figma sounds friendlier to designers and is a trap. Figma has no types, no review process and no history you can bisect. The moment a token needs a conditional — a value that differs by theme, platform or density — the design tool cannot express it and the pipeline breaks.
Code can express all of it, and designers get the result as native Figma variables that behave exactly like hand-made ones.
Northlight does not require you to rebuild your design system. Point it at your existing token file, let it generate a Figma library alongside your current one, and compare. Most teams cut over in a single sprint once they can see the diff.
Free for open-source and solo use.
Free
$19/month
Custom
Compact and comfortable variants now resolve from one definition rather than two parallel token sets.
No. They consume native Figma variables exactly as they do today. What changes is that the variables are generated, so they can no longer silently diverge from production.
Designers propose tokens through a pull request template that Northlight generates from a Figma selection. It takes about a minute and produces a reviewable diff.
Yes. Themes are a first-class dimension, and a token can resolve differently per brand, per colour scheme and per platform from a single definition.
Yes, permanently, including private forks of your own OSS project. Paid plans start at $19/month for commercial teams.
Similar products worth comparing before you commit.
Your calendar, rewritten every morning so you make fewer decisions
Unrelated domain — listed for teams comparing design-adjacent tooling.
A local-first sync engine you can drop into an app you already shipped
Observability a two-person team can afford to run and actually understand
Deploy previews for data pipelines, so reviewers see the diff in the data
Ranked by shared categories, tags and explicit alternative relationships.
A local-first sync engine you can drop into an app you already shipped
Deploy previews for data pipelines, so reviewers see the diff in the data
Observability a two-person team can afford to run and actually understand
Revenue analytics that tells you what changed instead of showing forty charts