Manifesto
A brand should be a system, not a file.
Brand Engine exists because every system that now speaks to a customer needs to know what your brand is — at request time, in a form it can actually read.
A brand is not a document
For thirty years the answer to "what is our brand?" has been a file. A guidelines PDF, a logo folder, a slide with three adjectives on it. Files describe a brand. They cannot run one.
Every system that touches a customer now needs an answer to that question at runtime: the chat agent composing a reply, the journey rendering an email, the assistant drafting a landing page. A file cannot answer at runtime. A structured, versioned identity can.
Identity is compiled, not written
We split what most tools conflate. Brand data is what you bring: philosophy, founder values, voice notes, documents, colors, logos. Detail is welcome; contradiction is expected.
Brand Identity is what comes out. Brand data plus a measured personality and a persona compiles into something a machine can read and a human can recognise — voice and principles, exact colors, a full logo system, all versioned.
That distinction is the whole product. Inputs stay editable and human. The output stays consistent and addressable.
One persona, every tool
Brand Engine is the roof, not another app in the stack. Tools live under it — AI Agents, Dialog Center, Playbook OS — and none of them owns the brand. They read it.
When the identity changes, they are told. A signed webhook invalidates their cache and the next request already uses the new version. There is no migration ritual, no re-briefing, no drift that surfaces three months later in a screenshot someone sends you.
Built for more than one brand
Agencies, holdings and founders with several ventures do not have a brand — they have brands. Brand Engine is multi-brand at the core: one account, many identities, strict boundaries between them, and an API that requires you to say which brand you mean.
Open at the edges
The identity you compile is yours and it is addressable: a documented HTTP API, an OpenAPI description, versioned bundles, signed webhooks. If a tool we do not build needs your brand, it can have it.
That is the bet. Not another interface for writing brand guidelines — an identity layer the rest of your stack can actually read.