Dembrandt vs Context.dev
Both extract brand data from a URL. The depth and purpose differ.
Context.dev is an API. It pulls brand assets from any website, logos and primary colors and fonts, and returns a lightweight JSON summary. It is built for apps that auto-style their UI to match a customer's brand. Dembrandt is a CLI. It extracts the full computed token set from a production page after render: every color with a WCAG grade, every font stack with its semantic role, spacing systems, motion values, and a drift score against the previous snapshot.
Comparison
| Context.dev | Dembrandt | |
|---|---|---|
| Primary use case | Brand data extraction for app personalization | Token extraction for drift tracking and AI agent context |
| Interface | REST API | CLI + API + web dashboard |
| Token depth | Colors, logos, fonts. A lightweight brand summary. | The full computed set: colors, typography, spacing, radius, shadows, WCAG grades |
| Semantic roles | Basic color palette | Color roles (surface, text, brand, accent) with usage context |
| Drift detection | No | Numeric drift score per deploy against a pinned baseline |
| CI integration | No | Yes. It runs as a CI step and fails the build on drift. |
| Agent interface | A JSON brand summary the agent parses | An MCP server with fifteen typed tools: tokens, palette, type, spacing, surfaces, drift, reports |
| Agent skills | None | 43 design and UX skills, so the agent applies the tokens correctly |
| File output | JSON | DESIGN.md, W3C DTCG JSON, CSS variables, a Tailwind v4 theme |
| Target user | Developers building multi-tenant apps | Design system teams, agencies, CI/CD pipelines |
Use Context.dev when
- You are building a multi-tenant app that auto-styles its UI to match each customer's brand
- You need a quick API call to get a brand's primary colors and logo
- You want brand data without running headless browser infrastructure
Use Dembrandt when
- You need the full computed token set with semantic roles and WCAG grades
- You want to track how tokens change between deploys and gate on drift in CI
- You are feeding brand context into an AI agent via MCP and need structured, deep token data
- You are auditing design system compliance, not personalizing app UI
The difference in depth
Context.dev is built for speed and breadth. It pulls a brand signature off any URL and returns it fast. That is the right trade when you need good-enough brand data to theme a UI across many customers.
Dembrandt is built for precision. It runs a full headless browser, scrolls the page, triggers lazy content, and reads computed styles after render. What comes back is not the CSS declaration. It is the value the browser settled on after cascade, inheritance, and dynamic theming. Drift scoring, WCAG grading, and agent context all need that depth. A brand summary cannot supply it.
Extract the full computed token set from any production URL:
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.