Brand guidelines · self-hosted
nexbrand keeps brand guidelines on your own server. Each client's colours, fonts, logos, type sizes and rules live in one place, every change carries a date, and whatever you enter is checked by computation.
Below, what nexbrand does ↓Example: Morgenrot Bakery
What nexbrand is
If you design or build for several clients, you usually hunt for the right blue in PDFs, old mails and design files. In nexbrand each client has its colours with roles and print values, its fonts with their licence, its logos with ground and clear space, a type scale, rules and examples. Everything sits in versions that never change once published.
Every client in one place, with access per client for people and teams. A new identity takes shape in the workbench, and the client picks a direction through a link, without an account.
A client calls about a reprint three years later? "As of" shows the guidelines exactly as they were then, and a project stays on the version it was made with.
Every version as CSS variables, Tailwind 4, SCSS or design tokens. A program reads the same values through the API, and an AI tool in your editor fetches them over MCP instead of inventing colours.
What nexbrand does
Brand guidelines are more than a list of colours. nexbrand records what applied when, computes whether it can be read, and hands it to clients, printers and developers.
Every change starts as a draft. Publishing gives it the day it applies from, and after that it never changes again.
A website or a trade fair stand may have colours of its own and inherits the rest from the client. It moves to a newer version only when somebody moves it.
Contrast of every colour pair by WCAG 2.2, colour vision deficiencies after Machado 2009, colours nearly the same by CIEDE2000. No hint is written by hand.
A few words, a picture or one colour turn into harmonies, neutrals, a font pair and a type scale, with a sample page and the checks next to it.
A link without an account shows the directions as sample pages. The client comments and chooses, and the choice becomes version 1.0.
A website, a GitHub repository or a PDF style guide provides colours, fonts and logos. The values are measured, not guessed.
Self-hosted
Brand guidelines are often confidential until they go public. That is why nexbrand runs on your server and sends nothing out that you have not explicitly allowed.
nexbrand runs in a Docker container on your machine. Clients, files and versions live in a single folder, and a backup takes all of it, every night on its own.
A font with an internal licence never leaves nexbrand as a file, not through public pages, not through a review, not through the API. Outside, only its name appears.
Without the operator's permission there is no AI at all. Whoever enters a service of their own sees every request word for word for 14 days, and nexbrand always measures the values itself.
Fetching websites and repositories is off until the operator allows it, and addresses in your own network stay blocked. On its own, nexbrand only asks once a day whether there is a new version.
Get started
It names the nexbrand image, a port and a folder for the data. That is all it takes.
After docker compose up -d you open nexbrand in the browser and enter the setup code from the log. The first account is the operator.
Build a new identity with the wizard, or record an existing one and give it the date it applied from.
Free and self-hosted
nexbrand is free software under the AGPL-3.0 and costs nothing. One compose file, one command, and your clients' brand guidelines have a home.