Frequently asked questions
Questions people actually ask
What is in the free adoption report?
From one repository and one design file, it returns the adoption percentage, the components most frequently reimplemented locally, and the count of unique variants of common elements such as buttons and inputs.
How does it find local copies of components?
It analyses the codebase to find where design system components are imported and where local reimplementations exist.
Does it look at design files too?
Yes. It finds detached and modified instances in design files and reconciles them with what is in the code.
Does it show why components are forked?
Yes. It identifies the components most often forked and why.
Can it check accessibility?
It tracks whether accessibility and token compliance hold in real usage.
What does it cost?
12 dollars per front-end engineer per month. Above 200 engineers it is 8 dollars per engineer, with multi-repository and design tool integration.
Can we run it without sending code outside the company?
Yes. The enterprise plan offers self-hosted analysis for companies that will not send code externally.
Why should I trust the component adoption calculator?
It is arithmetic on counts you take from a code search or a design file, worked out in your browser. It does not read your code; the free Design System Adoption Report finds imports, local reimplementations and variants from one repository and one design file.
How much of your product actually uses the design system?
Put in where a component is used from the design system and where local copies are used instead, plus the variants you have found. See the adoption percentage, the extra variants and their upkeep. Runs in your browser. No account, no card, no call.
Open the free toolIt runs in your browser. ProductLayers never sees your inputs.