Dembrandt vs Context.dev
Both extract brand data from a URL. The depth and purpose differ.
Context.dev is an API that pulls brand assets — logos, primary colors, fonts — from any website and returns a lightweight JSON summary. It is built for apps that need to auto-style their UI to match a customer's brand. Dembrandt is a CLI that extracts the full computed token set from a production page after full render: every color value with WCAG grades, every font stack with 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 — lightweight brand summary | Full computed token 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 — runs as a CI step, can fail builds on drift |
| MCP / AI output | JSON brand summary | DESIGN.md, W3C DTCG JSON, CSS variables — structured for AI agents |
| 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 optimized for speed and breadth: extract a brand signature from any URL and return it fast. It is the right tool when you need good-enough brand data for automatic UI theming across many customers.
Dembrandt is optimized for precision. It runs a full headless browser, scrolls the page, triggers lazy content, reads computed styles post-render, and returns exact token values: not the CSS declaration, but what the browser actually computes after cascade, inheritance, and dynamic theming. That depth is required for drift scoring, WCAG auditing, and structured AI agent context.
Extract the full computed token set from any production URL:
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.