Home

Brand Guidelines

How to represent BLACKBOX AI in press, partnerships, and integrations. Use the assets and rules on this page — and nothing else.

Logo

BLACKBOX AI wordmark on black
BLACKBOX AI wordmark on white
  • Keep clear space around the logo equal to the height of the icon mark.
  • Never use the wordmark below 90px wide; use the icon mark instead.
  • Use only the black or white version — never recolor, add gradients, or apply effects.
  • Do not rotate, stretch, outline, or place the logo on low-contrast backgrounds.
  • Do not rearrange the letterforms or pair the icon with a retyped name.

Name

Two forms only: the full brand name and the short form. The legal entity name in contracts and legal documents is separate and not covered by these rules.

The full brand name is written BLACKBOX AI — in metadata, headings, first mentions, and brand-level statements.

CorrectBLACKBOX AI
IncorrectBlackbox AI, BlackBox AI, BLACKBOXAI

In running text and product names, Blackbox is the short form after first mention.

CorrectBlackbox supports 35+ IDEs.
IncorrectBlackBox and bare BLACKBOX in prose

Chairman LLM is a product name and never takes an article.

CorrectChairman LLM evaluates every result.
IncorrectA Chairman LLM evaluates every result.

Color

The palette is monochrome first. Orange appears sparingly — selection, loading, and moments of emphasis — never as a fill for large surfaces.

Black#000000Primary background (dark), logo on light
White#FFFFFFPrimary background (light), logo on dark
Accent Orange#F97316Interactive accents, loaders, highlights
Selection Orange#F27500Text selection, emphasis moments
Zinc 700#3F3F46Muted UI, secondary surfaces
Zinc 400#A1A1AAMuted text, captions

Typography

Geist Sans — headings & body

Ship with every frontier model.

Semibold for headings with tight tracking; regular weight for body copy.

Geist Mono — labels, code & data

POST /v1/chat/completions

Uppercase with wide tracking for section labels; as-is for code and metrics.

Voice

Direct

Say what the product does in plain terms. No filler, no hype words that a developer would roll their eyes at.

Technical, not academic

Write for working developers. Name real models, real endpoints, real numbers — and link to the source.

Confident, not loud

Let 30 million users and shipped features carry the weight. Avoid exclamation marks and superlatives.

Need something not covered here?

For press assets, co-marketing, or usage questions, reach out and we'll get you what you need.

Contact Us