Every product team has two copies of its design system. One lives in Figma: the colours, spacing, icons and components that design approved. The other lives in production: the code customers actually use. On day one the copies match. A few months later they don't, and nobody can say by how much.
FISYCO exists to close that gap, and today it opens to everyone.
Key takeaways
- FISYCO is a design system assurance tool: it keeps the design you approve in Figma and the code you ship in sync, and shows where they diverge.
- Icons, illustrations and design tokens go from Figma to your repository as reviewed pull requests, by hand or after every publish in Figma.
- FISYCO reads your React code, ranks divergences from the approved design by reach and prepares fixes verified by rendering.
- It's free during the public beta, with every feature included and no card required.
Why we built FISYCO
Design system assurance means being able to show, at any moment, that production still matches the design system your team approved. Today most teams can't.
The gap rarely comes from one big mistake. A designer renames a variable and the code keeps the old name. A developer ships a quick fix with a hard-coded colour. A new icon lands in Figma and never reaches the repository. Each change is small and reasonable. Together they turn the approved system into a suggestion.
Industry surveys describe the same picture. In the Sparkbox Design Systems Survey 2022 (219 responses), 37% of respondents named parity between design and code as a top challenge. The zeroheight Design Systems Report 2026 (147 practitioners) found that only 40% of teams have any kind of token pipeline. The rest, in the report's words, are "manually syncing their tokens between design, docs and code."
We built FISYCO so that the difference between the two copies finally has an owner: a tool that sees both sides and reports every gap it finds. Measuring that gap honestly turned out to be harder than it looks. Our first measurement of a demo repository counted our own exported icons as hundreds of bypasses, which taught us to exclude generated code. We explain the mechanics in why production quietly drifts from your design system.
What FISYCO does today
Libraries: from Figma to code through a pull request
Connect a Figma file and a repository, and FISYCO turns design assets into code:
- Icons as React components, an SVG sprite or a package.
- Illustrations as SVG, PNG, WebP or AVIF files.
- Design tokens: Figma variables and styles as JSON, CSS, SCSS or TypeScript.
Changes arrive as a pull request, so they get the same review as any other code. Sync by hand or let FISYCO sync after every library publish in Figma. Variables come through the FISYCO plugin for Figma, so variables sync on any Figma plan.
Drift detection: find where production diverged
FISYCO indexes your code and compares it with the approved design. It lists every divergence it finds and ranks each one by how much of the product it touches. A divergence can be a colour that drifted, a token that exists in design but not in code, or a hard-coded value where a token belongs.
For many findings, FISYCO prepares a fix, verifies it by rendering and only then opens a pull request. Unverified fixes never ship, not even as drafts.
Components: see the impact before you rebuild
For component libraries, FISYCO watches changes to Figma components and tells you whether a change is likely to break the code that uses them. It doesn't generate components. It tells your team where to look before a rebuild starts.
Where it works
How to get started
- Create a workspace and a project.
- Connect your Figma account and a repository.
- Add your first library.
- Run a sync and review the pull request FISYCO opens.
The first sync sets a baseline, and FISYCO compares every new change against it.
Start with one project and one library. Icons show the whole loop fastest: publish in Figma, review the pull request, merge. Then connect your repository as the code side of the design system to see where production has drifted.
Frequently asked questions
Is FISYCO free?
Yes, during the public beta. Every feature is available, with no charge and no card required.
Does FISYCO change our code without review?
No. Every change arrives as a pull request in your repository, and your team decides whether to merge it.
What access does FISYCO need to our repository?
On GitHub, FISYCO installs as a GitHub App with read access to repository contents and write access to pull requests. Write access to contents is needed only if you want FISYCO to propose code fixes. FISYCO stores component names, file paths and line numbers, never the text of your code. It keeps the last 30 indexes, shows you a full access log and deletes everything derived from your code when you disconnect it.
Do we need Figma Enterprise?
No. Styles are read through the Figma API, and variables are sent by the FISYCO plugin, which works on any Figma plan.
Tell us what's missing
We're working closely with the first teams. If something is missing or gets in your way, write to us at hello@fisyco.com; it goes straight to the people building the product.
This blog is where we'll share what we learn. Coming up: how design systems drift, how to measure their health and how to move design tokens from Figma to code without manual exports.