Brand DNA is the per-brand artifact that captures everything Brandflux needs to render on-brand work. It is the wedge of the product. Without a published DNA, there is no DNA-anchored rendering, and without that, there is no brand-first creative claim.
What’s inside
Six field groups, all editable, most extracted from a single brand URL during onboarding:
- Palette. Primary, secondary, and up to four accents. Each color carries a usage note that guides layout decisions.
- Typography. Headline, body, and mono families with weights and sizes. If the brand uses an italic serif for emphasis, the system flags it during extract review and asks for confirmation.
- Voice. Three to five voice samples (a paragraph or two each) that capture the formal and informal registers. The Composer reads these at every generate to keep words on-brand.
- Imagery. Reference images marked “good” (the brand uses these) and “bad” (the brand avoids these). Three of each is the practical minimum.
- Mandatories and things to avoid. Logos, legal lines, banned phrases, banned colors. Anything required on every asset or refused on every asset.
- Brand Audience and Channel Audiences. The brand-wide audience model plus optional per-channel overrides.
How it gets created
A Brand DNA is typically extracted from a single brand URL: the home page, the product pages, the about page. Brandflux pulls palette, typography, voice samples, and reference imagery in one pass, then a human reviewer confirms or edits each field. The artifact is version-controlled. Published versions are the rendering anchor. Draft versions don’t ship to production renders.
Per-brand, not per-workspace
Each Brand in the workspace gets its own DNA. A creative-ops team running four client brands publishes four DNAs. The system enforces isolation: brand A’s voice samples can’t leak into brand B’s renders. This is the technical backbone of multi-brand operations.
Related on this site
- /product covers the DNA in the workflow context.
- /docs/brand-dna/anatomy is the field-by-field reference for builders.
- /use-cases/multi-brand-team shows how multiple DNAs work in practice.