Skip to content
Codz
Book a demoLog in

Brand guidelines

How Codz looks, and how to show it.

The mark, colours, type and words that make Codz recognisable — for anyone writing about it, building on it, or putting it on a slide.

02 / Lockup

Mark and name

Where the name sits beside the mark, set “Codz” in Inter at 590 with −1.2% tracking. The mark stands 1.375 times the type’s size, half an em from the word, on the same centre line.

Codz

Write the name with one capital: Codz — never CODZ or codz in a sentence. Products keep it first: Codz Remote, Codz Simulator.

03 / Clear space

Room to breathe

Keep a quarter of the mark’s width clear on every side — the same margin the app icon gives it. On screen, don’t draw it smaller than 16 pixels, the size of our favicon.

64px32px22px16px

04 / Misuse

Leave it as it is

The mark only works whole and upright. Don’t redraw it, add to it, or ask it to do what type should.

  • Don’t stretch or squash it.

  • Don’t turn it. The gap opens downward.

  • Don’t recolour it. It is black or white.

  • Don’t outline it or hollow it out.

  • Don’t pull the two parts apart.

  • Don’t set it where it can barely be read.

05 / Colour

Black, white and one blue

Codz is mostly black and white. Codz blue is the accent: it marks the next step, the ground our product stands on, and little else. Press a value to copy it.

  • Codz blueThe primary button, the blueprint ground and the closing band.
  • Blue on darkCodz blue as text and links on a dark page.
  • Blue, hoverA blue button under the pointer.
  • Night groundThe blueprint’s field in the dark theme.
  • BlackThe dark page.
  • Raised blackCards and windows on the dark page.
  • Off-white inkText on the dark page.
  • Grey inkSecondary text on the dark page.
  • WhiteThe light page, and the app icon’s tile.
  • Raised whiteCards on the light page.
  • InkText on the light page.
  • Slate inkSecondary text on the light page.

06 / Type

Inter, and a little mono

Inter for everything people read; the system monospace for small capital labels, the way the app’s status lines and the CLI speak. Headlines are tight at 510, body stays 400.

  1. Display64 / 1.0 · 510 · −2.2%The native workspace for every coding agent
  2. Section48 / 1.0 · 510 · −2.2%Bring your agents.
  3. Title40 / 1.1 · 510 · −2.2%A command center for coding agents.
  4. Lede24 / 1.33 · 400 · −1.2%Codz runs every agent you use in one native Mac window.
  5. Body15 / 24 · 400 · −1.1%The diff, the files, the browser and the bill beside the conversation. Free for every agent you run on your Mac.
  6. Label12 · mono · capitals01 / Agents

07 / Blueprint

The blueprint

Pictures of Codz stand on a rule taken from our development icon: a major line every four 26-pixel cells, a faint one in each. Blue says “this is Codz”; paper lets the product speak.

Fin
Paper

08 / Voice

Plain and exact

We write the way the app talks: short, specific, and only about what Codz does today.

  • Show the product, not a picture of it.

    Every picture of Codz on our site is the app itself, drawn live in the reader’s theme. Use the real thing, never a mockup of one.

  • Say only what’s true.

    Prices come from the plans, the changelog from what shipped. No invented numbers, quotes or customers.

  • Use the app’s own words.

    Labels, menu paths and shortcuts exactly as Codz shows them: Settings ▸ Account, ⌘K.

  • Weight, not colour.

    Hierarchy comes from size and weight. Blue is kept for the one thing to do next.

You’re welcome to use the name and mark to refer to Codz — in an article, a talk, or your integration’s docs. Please don’t use them in a way that suggests Codz made or endorses something it didn’t, or work them into your own logo. Anything else: can@codz.com.