Collect and AI
Guidelines from what already exists.
Many clients have an identity, it just is not written down anywhere clean. nexbrand reads it from their website, their GitHub repository or their old PDF style guide. The values are always measured; rules or your own AI service only sort them.
Collecting as a draft
Under Collect you choose a client or create a new one right there, name up to six sources and press “Collect”.
- Website: theme colour, styles in the page and up to ten style sheets, linked web fonts and self-hosted fonts, plus logos: pictures with “logo” in their name, the page's icon and the preview picture for social networks.
- GitHub repository: Tailwind configuration, token files,
package.jsonand style sheets, at most 40 files. For private repositories the operator stores a token. - PDF style guide: HEX, RGB, CMYK and Pantone values from the text of the first 80 pages, and the embedded fonts. The PDF goes into the client's files and never leaves nexbrand.
nexbrand merges colours less than 2 apart and shows each with its share, where it was found and what it was called there. Colours from a framework such as Bootstrap or Tailwind count only a tenth and are marked “from the framework”.
Without AI, nexbrand sorts by fixed rules: neutrals by lightness, the strongest colourful colour becomes the main colour, the next clearly different one the accent. You untick what does not belong, rename, and take everything as a draft “Collected on …”. It is published on the client page like any other.
Check against the CI
The second way of collecting writes nothing, it compares. Every colour found stands next to the nearest colour of the version that applies:
- Matches: a distance below 1.
- Nearly right: a distance below 8. The guidelines' colour is probably meant, and somebody measured it off a screenshot.
- Not in the CI: with its share of what was found.
Fonts with no match in the version are marked “Not in the CI”. That is how the agency finds the client page whose red has been slightly too orange for years.
Pavo saysDevelopers get the same check through the API and MCP, even for a whole style sheet with the colour pairs in it.
Font files only with a licence
nexbrand always takes the name of a font it found. It fetches the files only when you tick the font explicitly and confirm that there is a licence for it. Who confirmed it and when is written in the log and on the font itself.
A font of unknown licence stays “In-house only” and never leaves nexbrand as a file. Fonts linked through a well-known service for free web fonts count as free.
An AI service of your own, per account
nexbrand has no AI of its own and sends nothing to a service you have not entered yourself. If the operator allows it, every account enters its own service under My account, AI: address, key and model. Four tiles fill in the address of well-known services, Ollama for your own machine among them, and any other address with the usual chat interface works just the same. “Load the models” checks whether address and key are right.
The AI has exactly two tasks, and neither of them is free text:
- Sort what was collected: It sees only the measured values with share, name and source, and gives roles and names. A colour it names that was not measured is thrown away.
- Propose directions: hue, font pair and reasoning for the wizard. nexbrand computes the colours.
Bolts on the way out
Two switches
Collecting from websites and repositories and the AI service per account are off by default. Only the operator switches them on. PDFs always work, because they do not leave nexbrand.
What went out
Every request to the AI is listed in your account word for word for 14 days, stored encrypted. “Clear the list now” deletes it at once.
Never into your own network
Fetches go only to public addresses, and every redirect is checked again. An AI service at home needs the operator to allow its machine explicitly.
Previews through the server
The preview of logos found is fetched by the server, not by your browser. The other site does not learn who is looking.
Limits
Twelve seconds per fetch, size limits for pages, style sheets and files, 20 requests to the AI per minute.
Values always measured
Whether rules or AI sort them, every colour in the draft comes from the measurement. Invented values do not get in.