Talk about your brand

Brand book

Chainguard

Chainguard dresses supply-chain security as an engineering blueprint: ruled grids, mono labels and terminal panels say "built and verified", while the blurple accent, an octopus mascot and colour-coded tints keep it friendly rather than fearful. Our reading

The system

Fixed, everywhere

Chainguard logo
Logo
AaGellix Bold + Gellix Regular / Medium
Type pairing
  • #6226FB as the only interactive accent
  • #FBFBFF page with #0D161C ink
  • 1px ruled blueprint frame and dot grid
  • Gellix Bold heads at -3%
  • Roobert SemiMono caps eyebrows
  • square buttons with pixel arrows
  • the octopus mark

The one thing that varies

the tint hue (fuchsia, green, aqua, solar) that codes each card, tab and eyebrow highlight

Color, in proportion

lavender white #FBFBFF 76%ink #0D161C 13%white #FFFFFF 5%blurple wash #F8F6FE 2%graphite #192228 2%blurple #6226FB 2%

approximate share of the home page by visible background area (overlapping layers removed, rounded).

How loud each format gets

Silent
Quiet
Calm
WarmVideo lower third (customer story)
LoudSocial postLink share card (og:image)Video thumbnailEvent / webinar promo card
Loudest

Our engine's setting, built from their rules.

Every piece passes 7 checks

One accent

Blurple #6226FB only on buttons, links, arrows, logo, mono labels and at most one full closing band; tint hues only as small tabs, cursors, highlights or card headers.

Blueprint frame

Content sits in a centred column framed by 1px #E7E8E8/#EDEDED rules on #FBFBFF (or #3D4449 on #0D161C); no pill shapes or heavy shadows. Dots only in the hero band; chapters on plain #FBFBFF.

Type roles

Gellix Bold at -3% (or the Outfit 700 stand-in at -0.027em) for every head; Roobert SemiMono caps at 6% (DM Mono at +0.067em) for eyebrows and tags; regular sans 16/24 for body.

Logo

Real SVG: blurple on light, white on #6226FB or #0D161C; mark and wordmark together except avatar/app-icon uses.

Voice

Sentence-case heads without final stops, counts with "+", spaced dashes, short verb-first CTAs ("Talk to an expert", "Start for free"), no exclamation marks.

Numbers sourced

Every stat is one chainguard.dev states (e.g. 3,000+ images, 97.6% fewer CVEs, 4.7 on G2) or the customer's own, with its page.

Imagery

Product UI or terminals on graph paper, or real Chainguard people/customers; no stock, scenes or 3D.

Strategy

The trusted source for open source: hardened artifacts for every layer of the stack, from containers to libraries, CI actions and agent skills (paraphrase) Observed

01

Eliminate CVEs

Zero-CVE container images rebuilt from source daily, with remediation SLAs (paraphrase) Observed

02

Prevent malware

A vetted catalog of Python, Java, JavaScript, Go and .NET packages, CI/CD actions and agent skills (paraphrase) Observed

03

Avoid zero-days

Smaller images and same-day patched artifacts, powered by Athena (paraphrase) Observed

04

Govern and comply

Block artifacts from outside your org; provenance, SBOMs and FIPS images for FedRAMP (paraphrase) Observed

05

Zero developer friction

Drop-in adoption via 200+ Helm charts, the Guardener agent and a CLI (paraphrase) Observed

Full spec
For Observed
engineering and security teams, and the AI agents they build with; startups, Fortune 500s and government agencies (paraphrase)
Problem Observed
Developers and AI agents pull open source faster than reactive security can keep up; CVEs, malware and zero-days keep teams firefighting (paraphrase)
Promise Observed
Eliminate malware and vulnerability risk so developers can just ship (paraphrase)
Mission Observed
on a mission to be the safe source for open source

Proof behind each pillar

Values

Customer obsessed

make customers' lives easier and their software supply chains safer (paraphrase)

Observed
Bias for intentional action

"We prioritize, plan, test, fail, learn, and grow."

Observed
We do serious work without taking ourselves too seriously

"Serious about our mission, playful about everything else."

Observed
Trust each other and assume good intentions

good intentions by default; supportive, collaborative, fun (paraphrase)

Observed

Category. Software supply chain security / trusted open source artifacts ("Leader in the 2026 Magic Quadrant™ for Software Supply Chain Security") Observed

Why them

  1. Built from source and rebuilt continuously by the AI-native Chainguard Factory Observed
  2. 1-Day KEV SLA plus commitments for all container CVE severity levels Observed
  3. CVE backports for hard-to-upgrade Python, Java, JavaScript and Go library versions Observed
  4. Guardener agent migrates Dockerfiles layer by layer Observed
  5. FIPS 140-3 validated and SLSA L3 validated badges Observed

Boilerplate Observed

Chainguard is the trusted source for open source: hardened, production-ready artifacts for engineers and AI agents that help organizations prevent AI supply chain attacks, move faster with less toil and stay compliant; venture-backed, with Fortune 500 and industry-leader customers (paraphrase)

Taglines

The trusted source for open source Observed

Prevent AI attacks with trusted open source Observed

We’re building the trusted source for open source Observed

Switch to trusted open source with zero developer friction Observed

Works with what already works Observed

Start building with Chainguard Observed

Your open source foundation for the agentic coding era Observed

Build software securely with Chainguard Observed

Trusted by the best. Backed by results. Observed

Personality and voice

engineeredbut not corporateOur reading
confidentbut not alarmistOur reading
playfulbut not sillyOur reading
precisebut not denseOur reading
Full spec
  • Sentence case for every headline; capitals only in mono eyebrows and labels. E.g. "Prevent AI attacks with trusted open source" (home H1); "Works with what already works" (home)
  • Lead with a count and a plus sign. E.g. "3,000+ images with 97.6% fewer CVEs than public alternatives" (home); "1,000+ CI/CD actions that protect your most privileged code" (home)
  • Band heads make Chainguard the subject and the reader the beneficiary ("Chainguard [verb]s your ..."). E.g. "Chainguard lets you step off the CVE remediation treadmill to focus on building"; "Chainguard keeps your credentials out of attackers' hands without any incident response"
  • A threat stat in mono caps sets up each band, its last phrase highlighted. E.g. "THERE ARE 242 NEW CVES PUBLISHED EVERY DAY, UP 80%+ FROM 2025."; "A NEW PIECE OF MALWARE IS PUBLISHED EVERY MINUTE."
  • Headlines carry no final full stop; paired fragments take one each. E.g. "Start building with Chainguard" (all pages); "Trusted by the best. Backed by results." (/about-us, /customers)
  • Spaced dashes inside sentences. E.g. "Pull any artifact via CLI — or tell your agent to do it" (home); "Modern software runs on open source — and increasingly, it's being written by AI." (/about-us)
  • Short verb-first CTAs. E.g. "Talk to an expert"; "Start for free"
  • Repeats "trusted", "open source", "hardened" and "agents"; addresses developers and AI agents together. E.g. "trusted open source" (home H1, closing heads); "Developers and AI agents are pulling open source..." (/products/containers)

directtechnicalconfidentwry

  • Sentence case for every headline; capitals only in mono eyebrows and labels.
  • Lead with a count and a plus sign.
  • Band heads make Chainguard the subject and the reader the beneficiary ("Chainguard [verb]s your ...").
  • A threat stat in mono caps sets up each band, its last phrase highlighted.
  • Headlines carry no final full stop; paired fragments take one each.
  • Spaced dashes inside sentences.
  • Short verb-first CTAs.
  • Repeats "trusted", "open source", "hardened" and "agents"; addresses developers and AI agents together.
  • Observed: video thumbnails set titles in Title Case and product videos are named "Chainguard <Product> Demo" or "<Product> Workshop" ("Chainguard Workspaces Demo", "Why You Should Use Chainguard MCP", one "SHA Pinning is Not Enough!"); webinar cards stay sentence case with a colon split ("AI & the threat landscape: How the c-suite are governing AI before it governs them"). Sources: youtube.com/@chainguard, chainguard.dev/events (2026-11-10).

Their words

trustedopen sourcehardenedCVEsmalwareagentsagenticsupply chainzero-CVESLA

Never

Title Case Headlines (none seen)exclamation marks in headlines (none seen)closed-up em dashes (dashes are spaced)

Source: chainguard.dev/%20measure/home-desk.json%20+%20home-phone.json%20(2026-11-10)live computed styles, headless Chromium 1440x900 (2026-11-10)

  • Don’t title case
  • Don’t exclamation marks
  • Don’t fear-mongering without a fix

Source: chainguard.devchainguard.dev/about-uschainguard.dev/products/containerschainguard.dev/pricingchainguard.dev/careers

Color

Lavender-white #FBFBFF carries 88-94% of every page; #0D161C ink for heads and two dark bands on home; #6226FB blurple on buttons, links, arrows, logo and the closing band (2-3% of area); #F8F6FE wash for secondary buttons and the footer bar.

Full spec

Lavender-white #FBFBFF carries 88-94% of every page; #0D161C ink for heads and two dark bands on home; #6226FB blurple on buttons, links, arrows, logo and the closing band (2-3% of area); #F8F6FE wash for secondary buttons and the footer bar. A four-hue code (fuchsia #FD2BF2, green #04BD13, aqua #2BBAFD, solar #FD3964) appears only as small tabs, cursors and card headers, with matching tints and deep text tones.

  • Accent lives on buttons, links, arrows, logo and the one closing band.
  • Tint hues code categories; each card takes one hue (tab + tint + deep text).
  • Don’t pure white page grounds (white is for nav and cards)
  • Don’t bright tint hues as body text

Source: chainguard.dev/%20measure/home-desk.json%20+%20home-phone.jsonlive computed styles, headless Chromium 1440x900

Typography

The trusted source for open source

Aa
Gellix BoldDisplay · open stand-in
Aa
Gellix Regular / MediumText · open stand-in

Gellix Bold for every head at -3% (Outfit 700 stand-in at -0.027em) (hero 64/64, about hero 96/96, band heads 40/48 and 48/48, closing 72/72; phone 40/40 hero, 24-32 bands); Gellix Regular body 16/24 #565C60 and 18/24 leads; Gellix Medium 14 nav; Roobert SemiMono uppercase 14/20 at 6% for eyebrows, tags, tabs and footer labels; Roobert SemiMono (DM Mono stand-in) in the HTML terminal panel; Source Code Pro only inside supplied illustration files.

Full spec
Their faceUseLicenseOpen stand-in
Gellix Boldcommercial; open stand-in Outfit 700 at -0.027em (calibrated, see kit.typography.display)
Gellix Regular / Mediumcommercial; open stand-in Albert Sans 400 / 500 (Medium) / 600 (SemiBold) (calibrated)
Roobert SemiMonocommercial; open stand-in DM Mono 400 at +0.067em (calibrated)
Source Code Proopen (OFL), loaded by the site; appears only inside the supplied illustration files, never in HTML text (the stack-diagram terminal is Roobert SemiMono)
  • Bold sans for heads, mono caps for labels, regular sans for reading.
  • Don’t mono for headlines
  • Don’t positive tracking on heads

Source: chainguard.dev/%20measure/home-desk.json%20+%20home-phone.json

Graphic elements

Do #6226FB on a #FBFBFF page with #0D161C ink; about 2-3% of page area except the full #6226FB closing band (72px Gellix Bold #FBFBFF head, white-outline button, white logo right).

Blurple as the one accent · primary buttons, nav Contact us block, text links, arrows, logo, closing CTA band, mono labels on every page

Do 1px #E7E8E8/#EDEDED rules on #FBFBFF (#3D4449 on #0D161C); content column 1246px at 1440 (x 97-1343), 356px column box on phone (x 17-373, own rules at 17 and 372, inside outer rules at 0 and 389; text 322px at x 34); a faint SQUARE-dot grid (4px squares at 9% blurple, 24px pitch) in the hero band only; every other gutter is plain #FBFBFF; cells square-cornered. Bands that go edge to edge keep the column rules: the #0D161C dark band and the stack-diagram pinstripe field are full viewport width; the closing panel, the resources lavender half and the footer legal bar stay inside the column.

Blueprint frame · every page: centred column framed by 1px rules, bands and cells divided by rules

Do Roobert SemiMono 14/20 uppercase, 6% tracking, #7A7E81 (or #6226FB); last phrase on a tint (#FDDFFC, #DFF4FE, #E9FCEA); ends in a 10x16 solid block cursor (#6226FB, #FD2BF2, #2BBAFD or #04BD13) that blinks.

Mono caps eyebrow with a colour highlight and blinking cursor · home band intros, containers "WHY CHAINGUARD?", "LEARN MORE ABOUT TRUSTED OPEN SOURCE", "CHAINGUARD CONTAINERS" hero label

Do one hue per card: tint ground (#FEF5FE / #F2FDF2 / #F5FCFF / #FEF6F6), headline in the deep tone (#A10099 / #108000 / #006A97 / #B20028), 76x29 solid tab in the bright tone (#FD2BF2 / #04BD13 / #2BBAFD / #FD3964) flush top-right or under the row.

Colour-coded tinted cards with a corner tab · containers stat cards, about values, home feature-card headers

Do 0px-radius buttons, Gellix Bold 18, 16px padding, followed by a small dotted pixel arrow; product icons are 16px pixel-grid glyphs in #6226FB; checkerboard of purple squares on covers.

Square blocks and pixel-dot arrows · every CTA and text link; product-suite icons; guide cover pattern

Do Gellix Bold, letter-spacing -3% (with the Outfit 700 stand-in: -0.027em), line-height 1.0-1.2, #0D161C; 64-96px heroes, 40-48px band heads, 72px closing band.

Gellix Bold heads at -3% · all headlines

Specimens use sample copy, not Chainguard’s.

1px ruled frame around a centred column (a square-dot grid in the hero band only); bands and cells divided by rules; square-cornered buttons and nav blocks; 8px feature cards with a colour header field; mono tags (BLOG POST, GUIDE, CASE STUDY, POPULAR) as small filled or outlined rectangles; blinking block cursors; colour tabs 76x29 on tinted cards.

Full spec
  • Group content in ruled cells; keep corners square except media cards (8px).
  • Don’t pill shapes
  • Don’t heavy drop shadows

Source: chainguard.devchainguard.dev/products/containerschainguard.dev/pricing

Iconography

Pixel-grid icons: product-suite glyphs as 16px blocky shapes in #6226FB, dotted pixel arrows after every CTA, pixel chevrons on accordions; thin outline checkmarks and tier icons on pricing; solid social icons in the footer.

Full spec
  • Pixel-block glyphs in blurple for product and navigation icons.
  • Don’t rounded line-icon sets for product icons

Source: chainguard.dev/products/containerschainguard.dev/pricingchainguard.dev

Illustration

No drawn illustration.

Full spec

No drawn illustration. "Illustrations" are product UI and terminal panels: light UI cards and black terminal windows with monospace output set on tinted graph-paper grids (pink, green, cyan), wide card headers filled with a flat tint colour (#FD2BF2, #2BBAFD, #04BD13) holding a UI screenshot or chart, and a stack diagram of tiles around the mark. Collateral covers (guides) use dark violet with a purple pixel-checker band.

  • Show the product or the terminal, on graph paper, never a scene.
  • Don’t inventing an illustration style
  • Don’t 3D or isometric art

Source: chainguard.devchainguard.dev/products/containers

Photography

People only, never product.

Full spec

People only, never product. Candid team and event photos in natural warm colour (stage talk under blue light, crowded office party, retro-tracksuit team night, octopus mascot), cropped 4:3 with 8px corners in a row of three; exec headshots on dark gray studio grounds, square with 16px corners; customer-story covers are documentary video stills of customers, dark and moody, 5:7 portrait. Photos sit in ruled cells and never carry text on top.

  • Real Chainguard people and customers, candid or interview stills.
  • Don’t stock photography
  • Don’t text over photos

Source: chainguard.dev/about-uschainguard.dev/careerschainguard.dev/customers

Interface & layout

The page, band by band

Nav
Hero
Logo grid
Scroll-fill statement
Feature stack: Eliminate CVEs
Feature stack: Prevent malware
Feature stack: Avoid Zero-Days
Stack diagram
Dark adoption band
Compliance accordion
Resources

Buttons

Primary action
Primary: 58px tall · 16px sides · 0px corners · 18px, weight 700 · #6226FB fill, #FFFFFF text
Secondary action
Secondary: 58px tall · 16px sides · 0px corners · 18px, weight 700 · #F8F6FE fill, #6226FB text
Full spec

Announcement bar (#F1ECFE) over a 64px white nav with square blocks for Log in (#F8F6FE) and Contact us (#6226FB) at the right edge. Centred column framed by 1px rules (1246px at 1440; 356px column box on phone, text 322px inside it) (square-dot grid in the hero band only). Home: centred hero (H1, sub, two square buttons), 5x3 ruled logo grid, big centred statement, three feature stacks with a sticky side-tab rail, dark #0D161C bands, compliance band, resources, full #6226FB closing band, four-column link footer, #F8F6FE bottom bar. Phone: single column, full-width buttons, purple square menu button.

Measured from 's .

Spacing

MeasureDesktopPhone
Page margin96px16px
Section padding64px48px
Hero text widthmax 729px, centeredfull width
Card gap0px0px
Navigation64px64px

Type, at size

Hero H1

Gellix Bold · 64px (phone 40) · line 1 · tracking -1.73px · weight 700

Closing band head

Gellix Bold · 72px (phone 40) · line 1 · tracking -1.94px · weight 700

Statement

Gellix Bold · 48px (phone 32) · line 1.1 · tracking -1.3px · weight 700

Band head (H2)

Gellix Bold · 40px (phone 24) · line 1.2 · tracking -1.08px · weight 700

Card head (H3)

Gellix Bold · 24px (phone 18) · line 1.33 · tracking -0.65px · weight 700

Cell head

Gellix Bold · 18px · line 1.33 · tracking -0.18px · weight 700

Lead / body

Gellix Regular / Medium · 16px · line 1.5 · weight 400

Nav / footer link

Gellix Regular / Medium · 14px · line 1.43 · weight 400

Accordion item

Gellix Regular / Medium · 16px · line 1.25 · tracking -0.144px · weight 500

Button label

Gellix Bold · 18px · line 1.33 · tracking -0.18px · weight 700

Eyebrow

Roobert SemiMono · 14px (phone 12) · line 1.43 · tracking 0.94px · weight 400

Footer label / EN

Roobert SemiMono · 12px · line 1.67 · tracking 0.8px · weight 400

Tag chip

Roobert SemiMono · 14px · line 1.29 · tracking 0.14px · weight 400

Terminal text

Roobert SemiMono · 12.3px (phone 9.8) · line 1.45 · weight 500

Cards

LabelCard title, one line

One or two sentences on what this does for the reader.

LabelCard title, one line

One or two sentences on what this does for the reader.

Card: 8px corners on the surface band, 0px apart.

Motion
Mono eyebrows end in a blinking colour cursor; the long home statement H2 fills from gray to ink as you scroll; side tabs switch feature stacks.
Buttons
square

Page anatomy

How Chainguard’s own landing pages are built, observed on chainguard.dev, 2026-11-10. The full measurements are in spec.md.

Navigation
Sticky 64px white bar of ruled cells: logo cell, six text-link cells, then on the right a theme-toggle cell, an EN language cell, a lavender 'Log in' block and a solid blurple 'Contact us' block, both full bar height. Every cell is separated by a 1px #EDEDED vertical rule.
Hero
Centred type-only hero inside the ruled column on #FBFBFF: two-line Gellix Bold 64px headline, a two-line grey sub, then a pair of square 58px buttons (solid blurple primary, lavender secondary). Behind it, and only here, a 24px-pitch grid of tiny square dots fades out under the text via a radial #FBFBFF mask. No image, no proof row.
Customer logo grid + G2 rating
Ruled 5x3 grid of 15 full-colour customer logos under a 64px header row: mono caps line left, G2 logo + 5 stars + '4.7 STARS ON G2' right. Seven cells carry a tiny CASE STUDY chip in their bottom-right corner.
Scroll-fill statement
One centred three-line Gellix Bold statement, alone in the ruled column with large vertical padding. Words start grey and fill to ink as the reader scrolls.
Problem-led feature stack (three tabs: Eliminate CVEs, Prevent malware, Avoid Zero-Days)
The page's long middle: a sticky tab card in a left rail and, on the right, three stacked chapters. Each chapter is a mono threat stat with a highlighted phrase and blinking colour cursor, a 40px band head, one wide feature card (colour field with product UI on top, white body below), a 2x2 grid of ruled cells each with a short head and a graph-paper illustration, and a customer-story card. Each chapter has its own hue: fuchsia, aqua, green.
Ruled spacer row
An empty 64px row of the ruled column between major bands (repeats before the stack diagram, compliance, resources and the closing band).
Stack diagram ('Designed to fit securely within the rest of your stack')
Left-aligned head and paragraph over a lavender pinstripe field, then a centred architecture diagram: a blurple-outlined lavender panel holding a HARDENED ARTIFACTS pill, a PREVENTION label, a black docker-pull terminal, a DETECTION label and a white VULNERABILITY SCANNING tile.
Dark adoption band ('Switch to trusted open source with zero developer friction')
Full-bleed #0D161C band (x 0-1440, gutters dark too) with the same ruled column drawn in #3D4449 at x 97 and 1343: a centred white 48px head, a three-cell row of short heads with dark UI images, a two-column integrations block (head, paragraph, link left; 6x3 grey integration icons right), and a raised customer-story card.
Compliance accordion ('Enforce your organization's compliance standards')
Two columns in the ruled frame: head, paragraph and a three-item accordion on the left; a 500x450 product screenshot on a pale panel on the right that swaps with the open item.
Resources ('Learn more about trusted open source')
Split band: left half #F8F6FE with a mono heading and one featured guide card; right half a ruled list of seven resource rows, each a bold grey title and a mono type label.
Closing CTA band ('Start building with Chainguard')
Solid blurple panel filling the ruled column: a 72px two-line head in #FBFBFF top-left, then an email field with an outlined 'Talk to an expert' button, and the white Chainguard logo bottom-right.
Footer
Ruled four-column link footer on #FBFBFF, a utility row (theme toggle, social icons, blurple 'Talk to an expert' block in the last column), and a #F8F6FE legal bar with copyright left, centred blurple logo and legal links right.

Source: chainguard.dev/%20measure/home-desk.json%20+%20home-phone.jsonmeasure/about-desk.json + about-phone.jsonmeasure/containers-desk.json + containers-phone.jsonmeasure/pricing-desk.json + pricing-phone.json

In use

Full spec

From chainguard.dev pages, the homepage og:image and the og:image share cards of 8 Unchained blog posts; no organic social posts, ads, decks or emails were reachable.

Our setting for each format

FormatLoudnessMust appearWhat varies
Landing page#FBFBFF page, #F1ECFE announcement bar, 64px white nav with square Log in (#F8F6FE) and Contact us (#6226FB) blocks. Centred hero in a 1px-ruled column with dot grid: Gellix Bold 64/64 H1 at -3%, 16/24 #565C60 sub, square 58px #6226FB "Talk to an expert" + #F8F6FE "Start for free" with pixel arrows. Ruled logo grid with a mono caps header and G2 rating; mono eyebrow with highlighted phrase and blinking cursor over each 40/48 band head; feature cards with tinted header fields and graph-paper UI; #0D161C band with white heads; #6226FB closing band (72px #FBFBFF head, email field, outline button, white logo); four-column link footer with mono labels.
Social postOne flat ground (#FD2BF2, #6226FB or #060C10), square pixel tiles only at the left and right edges, one mono caps eyebrow over a centred Gellix Bold headline of at most 3 lines in white. Nothing else.Ground colour per campaign (fuchsia #FD2BF2 for launches, blurple #6226FB, near-black #060C10 for recaps); tile pattern; eyebrow present or not. Two other observed card families may replace the tile card: the editorial bar card (#FBFBFF grid ground, headline set in solid #FD2BF2 / #6226FB bars, #14003D icon square) and the frame card (#192228 or #6226FB ground, white hairline frame with square nodes, headline in white bars). Portrait 1080x1350 not added: no portrait posts observed. Observed 2026-11-10: no organic announcement posts reachable (X empty logged out, Instagram login wall, LinkedIn not visited) and no single-image offer ads (Meta: no Chainguard advertiser; Google image ads are Google-assembled), so this row is unchanged; the closest observed family for an announcement is the Event / webinar promo card (colour top band with lockup and mono date, mono eyebrow with square cursor, left bold headline; ref/examples/event-1.png).
Link share card (og:image)Same families as the Social post row at 1.91:1: edge-tile announcement card, editorial bar card, white-hairline frame card, or flat #6226FB with the centred white logo (homepage).Ground per post; homepage card is logo only.
Video thumbnailFlat #6226FB or #0D161C ground, small white lockup top left, a big white bold headline stacked left, and one right-hand visual: a presenter cut-out, a product pixel icon on a colour panel, or nothing.Speaker variant (cut-out right, pixel squares in the top-right corner) or product-demo split (left 61% ground, right 39% #6226FB/#FD2BF2 panel with the product's white pixel icon); text-only recap with corner squares. One campaign thumbnail ("Open source is DYING") uses a full-bleed photo with pixel-art props and a pixel font; keep that to campaign films.
Event / webinar promo cardColour top band (#6226FB, #FD2BF2) or a hairline-ruled top row on #14003D, holding the white lockup left and a mono caps date right; below, a mono caps eyebrow with a square cursor over a left-aligned bold headline of 2-4 lines.Speaker column on the right (1-3 rows split by 1px rules, name bold, role and company in mono, cut-out photo); Learning Labs series uses big #6226FB blocks and no band; conference cards use a ruled grid (logos, date, venue photo duotoned blurple, booth line) or a logo lockup over a #6226FB bottom band. Scoped to event and webinar promotion.
Video lower third (customer story)A solid white block bleeding off the near edge, then the name in white bold and the role in white regular beneath, on the subject's open side of the frame.Left or right side, whichever is open; burned-in caption on a dark translucent bar at the bottom centre when present.

Ads

Rules

Do

  • Keep #6226FB for action, links and the logo.
  • Use only numbers Chainguard states or the customer's own.
  • Frame content in 1px ruled cells.

Don’t

  • rounded pill buttons
  • stock imagery
  • unsourced security stats

Source: chainguard.dev

Steal this kit

Your name and logo, Chainguard’s system.

Comes with you

  • Color roles and how much of each
  • Type pairing, with open fonts
  • Voice rules the writing check enforces
  • Icon, photo, illustration and motion recipes
  • The strategy frame, to fill with yours

Stays yours

  • Your name and logo
  • Your proof: numbers, customers, quotes
  • Your purpose and claims. Theirs aren’t yours to make

Talk about my brand Use this brand in Claude

Hand it to a developer

Your brand next

Get your brand audit Put your brand in Claude What goes in a brand book

What Chainguard doesn’t publish
  • No brand, press-kit or media-kit page: /brand and /brand-assets 404, /press redirects to /newsroom, which has press links and coverage but no logo downloads or guidelines. Nothing in this book is "published"; colour names come from the site's own CSS classes (brand-non-text-blurple, -fuchsia, -aqua, -solar) and are observed.
  • No official clear-space, minimum-size or logo misuse rules; logo variants were serialized from the inline nav SVG (on-light, on-dark, mark-only crops of the same paths) plus the favicon.
  • Several CSS tokens (--primary-blue #3443f4, --primary-dark-purple #14003d (seen only on one blog share card), cyan, yellow, orange, pink) are declared but were not seen in use on the studied pages.
  • Deck: no Chainguard deck or slide template seen on the site; only a guide cover (illo-ciso-guide-cover.png) hints at collateral style.
  • Email: no Chainguard marketing email reviewed.
  • Dark mode exists (theme toggle in nav and footer; logo class dark:text-white) but dark-mode colours were not measured.
  • Fonts: Gellix and Roobert SemiMono are commercial; calibrated stand-ins are Outfit 700 (display), Albert Sans 400/500 (body) and DM Mono 400 (mono), numbers in kit.typography.
  • measure/*-desk.json and ref/*-desk-*.png were captured with the Qualified 'Linky' chat panel docked (page 1040px wide). kit.spec.page/bands/layout were re-measured at the resting 1440 width with that widget blocked; the stored desktop measure files and screenshots were not regenerated.
  • Home: no postal address or phone number is published in the header or footer.
  • Home stack diagram side groups and the statement fill are scroll animations; the anatomy gives the resting state. The stack diagram is HTML/CSS, not an image file, so it has no slot asset.
  • Social post: no organic posts were reachable (X shows nothing logged out, Instagram is login-walled and not linked from the site, Bluesky chainguard.dev has 0 posts, LinkedIn not visited). The 1080 square anatomy is derived from 8 observed og:image share cards; no portrait (1080x1350) evidence, so no portrait row.
  • Library: Chainguard publishes no reusable pattern/texture/background files (no CSS background images on 20 crawled pages; the pixel-block borders exist only baked into blog/event covers), no device-shot product photography, and no standalone spot illustrations beyond the pixel icon set; leave those slots out rather than drawing them. Blog factory photos were generic stock and were dropped.
  • Customer-story icon tiles, the pixel-dot arrow and the footer theme toggle are inline SVGs on the site; they were serialized from the live page into home/ (see slot_assets). The nav sun icon and social icons were not serialized.
  • Dark-mode toggle: only the light (sun-active) state was captured; the moon-active state is not in the assets.

Each value is marked published, observed, our reading or our recipe, with its source. Checked 2026-11-10. Not affiliated with Chainguard.

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.