Deliverables in your brand, not ours.
A brand kit is a folder you upload into a workspace: your print stylesheet, your fonts, your logos, the masters you write to, and a small manifest naming them. From then on the work comes out looking like you sent it.
Six steps, then every document follows it.
Upload your brand as a folder and every document that workspace produces is rendered with your stylesheet, fonts and page setup instead of a house template, and the specialists writing it are told where your rules are. Nothing about your brand lives in the platform; the contract is one small manifest.
| Step | What happens |
|---|---|
| Package it | A folder holding your print stylesheet, your fonts, your logo files, the master documents you write to, and a brand.json that names them. Zip it. |
| Upload it | Settings → Documents → Brand kit, in the workspace that should use it. It unpacks into that workspace’s own files, and the panel shows what it resolved to. |
| It belongs to that workspace | Kits are found per workspace, so the brand you use for one client, fund or division is invisible to every other workspace on the box. |
| Documents render through it | A finished document is rendered from inside your kit, so your page size and margins, your @font-face files, your logos and your running feet all resolve by relative path. Plain Markdown comes out in your type and page setup too. |
| The specialists are told | Every dispatch in that workspace names your kit: the instructions file agents must read first, the manifest, the stylesheet, and the masters they copy structure and class names from. Your rules travel with the work instead of living in a prompt. |
| Change it, and the work follows | Upload a new version and the next document uses it; re-generate an old one and it comes back in the new brand. Remove the kit and the house template quietly takes over again. |
The manifest needs one thing: the path to your stylesheet. A base directory, an instructions file and a masters directory are optional. Paths must stay inside the kit, with no absolute paths and nothing reaching upward. A manifest that fails that check is ignored with a warning rather than applied. Fonts and images are read from your own files; rendering fetches nothing from the network.
One brand per workspace, none in the platform.
One client, one brand.
Kits are found per workspace, so the brand you use for one client, fund or division cannot reach another. An agency or a multi-strategy firm can run several, side by side, on one box.
Nothing about you is in our code.
The contract is a manifest shape. We ship no customer branding, so your kit is yours to change without waiting for a release.
Told, not prompted.
Every dispatch in that workspace names your instructions, your stylesheet and your masters, so the specialist writing the document reads your rules rather than inventing a house style.
Send us your brand and see it render.
Bring a kit, or the brand guide you already have, and we will produce a real document from it on a call.