Logo variants
Keep the brand’s logo variants together.
Give every brand a shared reference
Keep logos and marketing collateral together in each brand’s public kit.
Each brand gets 30 built-in kits across core identity, visual language, digital and web, social and ads, marketing, print and merchandise, media and governance, plus its own custom kits. Files live in R2, colours and fonts generate CSS, Tailwind and DTCG design tokens, and any kit or the whole brand downloads as one ZIP. All 80 connected domains were imported from their /brand/ pages, and brand-kit.<domain> serves each shared brand on its own domain. The public inventory exposes only brand IDs and whether each brand is shared.
What Brand Kits does for you.
Keep the brand’s logo variants together.
Collect the materials that support the brand’s marketing.
Present the kit on the domain’s public brand-kit page.
A suggested path for Brand Kits. What you can do depends on your access in the app.
Start with the brand you are working on.
Inspect logo variants and available collateral.
Refer to the public kit when preparing your design work.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each brand gets 30 built-in kits across core identity, visual language, digital and web, social and ads, marketing, print and merchandise, media and governance, plus its own custom kits. Files live in R2, colours and fonts generate CSS, Tailwind and DTCG design tokens, and any kit or the whole brand downloads as one ZIP. All 80 connected domains were imported from their /brand/ pages, and brand-kit.<domain> serves each shared brand on its own domain. The public inventory exposes only brand IDs and whether each brand is shared.
The design system that implements a brand in product UI stays in Design Systems; reusable layouts stay in Templates.
6 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
brand-kits.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.