Dembrandt vs zeroheight
zeroheight documents what your design system should be. Dembrandt measures what your production site actually is.
zeroheight is a design system documentation platform: it syncs tokens and components from Figma and code into living style guides teams can browse. Dembrandt is a CLI tool that extracts live design tokens from any URL and scores how much they drift between deployments. One is the reference. The other is the audit.
Comparison
| zeroheight | Dembrandt | |
|---|---|---|
| Source of truth | Docs synced from Figma and Storybook/code | Live production DOM — what users actually see |
| Token extraction | Pull token values from connected Figma libraries | Automated CLI extraction from any URL in seconds |
| Drift detection | No drift scoring against the live site | Numeric drift score per deploy, CI-ready |
| CI/CD integration | Doc publishing, not deploy pipelines | Runs in GitHub Actions, GitLab CI, any CI |
| Scope | Living documentation, adoption, governance | Design token extraction and drift monitoring |
| Baseline comparison | Version history of the documentation | Pin any snapshot. Every deploy scored against it. |
| Access model | Hosted style-guide portal for teams | CLI + API + web dashboard |
| Pricing model | Per-seat SaaS | Usage-based, free tier available |
Use zeroheight when
- You want living documentation that stays in sync with Figma and code
- You publish usage guidelines, component specs, and do/don't examples
- You need a browsable portal for designers, engineers, and stakeholders
- You track design system adoption and governance across teams
Use Dembrandt when
- You want to verify that production matches the system, not just the docs
- You need drift flagged automatically on every deploy
- You run CI/CD pipelines and want a build step that fails on brand regression
- You manage multiple client sites and need cross-domain token tracking in one place
The gap zeroheight does not cover
zeroheight works from the design side in. It pulls token values and component specs from Figma and your codebase and publishes them as documentation. The source of truth is what your team authors and connects.
That leaves one question unanswered: does your live site match it? zeroheight does not read your production DOM, compute your rendered token values, or score drift between releases. That gap is where the shipped UI silently diverges from the documented system.
Dembrandt reads what the browser actually renders after full page load, including overrides from application CSS, third-party scripts, and dynamic theming. It surfaces the gap between what was documented and what shipped.
Run a one-off extraction on any URL with no account required:
npx dembrandt your-site.comTo enforce drift in CI, get an API key and add --key $DEMBRANDT_KEY to your deploy step. Full setup: cloud drift CI recipe.