Home · Platform · Platform · The brand engine
Your brand, read from your own site.
Give Noice.work your website address and it reads the site's real, rendered styles — the colours it actually paints, the type it actually sets, the shapes its buttons actually take — and generates a complete design language from the evidence: not a theme picked from a gallery, and not a model's impression of your brand, but a measured one.
Observed, then decided — in that order
The import is two deliberate stages. First, observation: every distinguishable colour the site paints, with how much of the page it covers and which elements carry it. Then casting: rules in code — not a model's judgement — assign what was observed to jobs. The largest painted background becomes the paper; the colour your buttons actually wear becomes the interactive colour; the colours your site paints its bands in become your band palette. Every value carries its provenance, so the workbench can always tell you whether a colour was observed on your site, chosen by a person, or a default we supplied — and the import says out loud when it could not verify something rather than quietly inventing it.
A design system, not a stylesheet
What comes out is a governed token system the entire component catalogue is bound to: grounds and inks solved for contrast, a spacing and type scale, corner and edge treatments — the machinery of a design system, generated. Every page, form and video the agent composes wears it structurally; there is no way to compose off-brand, because the components have no off-brand mode. When you want to adjust it, the workbench edits the same tokens with live preview, contrast checking and the same audit trail as everything else.
When the front door is locked
Roughly half of enterprise sites sit behind firewalls that refuse automated reads, and we would rather tell you that than pretend. When the capture is refused, the brand is built in the workbench instead — same token system, same result — and we help. The claim is bounded on purpose: your own site, read and verified up front, with a stated graceful path when a firewall says no.
Questions people ask
Our brand lives in Figma, not on our website. Can we start from that?
The importer reads served websites, because a live site is the one artefact that reflects what your brand actually looks like in production. Brand guidelines and Figma files are inputs a person applies through the workbench, where every token is directly editable.
What happens when we rebrand?
The brand is data, not templates: re-import or edit the tokens and every page re-renders in the new language on the next request. There is no template migration, because there are no templates.