Dembrandt vs Frontify
Frontify stores what your brand should be. Dembrandt measures what your production site actually is.
Frontify is a brand management portal. It holds approved logos, guidelines, and documentation. Dembrandt is a CLI. It extracts the design tokens a URL actually renders and scores how far they drift between deployments. One is the reference. The other is the audit.
Comparison
| Frontify | Dembrandt | |
|---|---|---|
| Source of truth | Brand guidelines uploaded to Frontify by hand | The live production DOM. What users actually see. |
| Token extraction | Import from Figma or define manually | Automated CLI extraction from any URL in seconds |
| Drift detection | No drift scoring between releases | A numeric drift score on every deploy, ready for CI |
| CI/CD integration | Not designed for deploy pipelines | Runs in any CI. --compare exits 1 on drift. |
| Scope | Full brand asset management: logos, fonts, docs | Token extraction, drift monitoring, and a brand guide PDF export |
| Baseline comparison | Version history of guidelines | Pin any snapshot. Every deploy scored against it. |
| Access model | Centralized brand portal for teams | CLI + API + web dashboard |
| Contrast grading | Not scored against the shipped page | --wcag grades every palette pair AA and AAA with exact ratios |
| Multi-page runs | Whatever was uploaded to the portal | --crawl and --sitemap read a whole domain in one run |
| Private pages | Uploaded by hand | --cookie and --header extract behind a login |
| Agent access | Brand assets a person downloads | An MCP server with fifteen tools, plus 43 design skills |
| Where the team sees it | A portal someone remembers to open | Drift posted to Slack from the CI report |
| Pricing model | Per-seat SaaS | The CLI is free and open source. An account is needed only for cloud sync. |
Use Frontify when
- You need a centralized portal where marketing, design, and legal access approved assets
- You publish brand guidelines, tone of voice, and logo usage rules
- You manage multiple brands or sub-brands and need a structured library
- You distribute assets to agencies and external partners
Use Dembrandt when
- You want to verify that production matches your design system, not just your documentation
- 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 Frontify does not cover
Frontify works top down. You define the brand, upload the assets, share the portal. The source of truth is whatever your team documented.
One question stays open: does the live site match it? Frontify cannot know. It does not read your production DOM, compute rendered token values, or score drift between releases. That blind spot is where tokens quietly walk away from the guide.
Dembrandt reads what the browser actually renders after full page load, including overrides from application CSS, third-party scripts, and dynamic theming. It measures the gap between what was documented and what shipped. Nobody has to open DevTools and guess hex codes to find it.
Run a one-off extraction on any URL with no account required:
To enforce drift in CI, get an API key, then run --compare <baseline> --key $DEMBRANDT_KEY in your deploy step. It exits 1 when the tokens move. Full setup: cloud drift CI recipe.
Other comparisons
Every tool here solves a different part of the problem. The full list says which does what.