The rules of the road.
How to talk about Common Compute, how to use our logo, and what we will and won't lend our brand to. Built to be light enough to read once and forget — the constraints are small, the intent is everything.
Need the assets right now? Skip to /press.
Direct, restrained, honest about tradeoffs.
We sell economic transparency to a market saturated with marketing that hides it. Our copy should sound like a senior engineer talking to a senior engineer — never breathless, never defensive, never the person who would high-five you for buying their product.
The lockups and how to use them.
Three lockups, all in the same file family at /press. Use them in this order of preference:
- Layered logo — network mark + wordmark. The default for any context where the brand needs to be unambiguously named (press, partner pages, conference signage).
- Wordmark only — for small contexts where the mark would be illegible (footer, email signature, single-line headers under ~40px).
- Symbol only — the interlocking-C monogram. For favicons, social avatars, and app icons. Don't pair the symbol with the wordmark on its own line — that duplicates the layered logo and reads as a mistake.
A small palette that does a lot.
Common Compute is dark-mode-first by default. The palette is small on purpose; the brand should read as considered, not crowded. Use one accent per surface — the electric blue is the workhorse, the green and amber are signal-only.
Inter Tight + JetBrains Mono. No exceptions.
Two families. Inter Tight ExtraLight (200) is the display face — it's what the wordmark uses, and it's what every headline on the marketing site uses. Inter Tight at regular and medium weights covers body copy. JetBrains Mono handles every place we need a monospaced rhythm: code, eyebrows, version numbers, metric values.
Letter-spacing is tight on display, neutral on body, generous on the mono. Don't use bold-italic combinations — restraint is part of the look.
Where the assets come from.
Every brand asset is regenerable from source — there's no designer's laptop holding a single source of truth, and no private Figma file you'd need to ask us for. The pipeline lives in the repo at scripts/ and produces both the web SVGs and the Mac app's asset catalog entry from the same step.
- Mark vector.
scripts/trace-brand-mark.shthresholds the canonical PNG, runs potrace with the settings we've tuned for the interlocking-C topology, and bakes the resulting path into a clean 256×256 viewBox withfill="currentColor"so both CSS and SwiftUI template rendering Just Work. ~6 KB output, deterministic for a given input PNG. - Wordmark vector.
scripts/outline-wordmark.pyreads the bundled Inter Tight variable font, instances it at ExtraLight (weight 200), and emits the “Common Compute” wordmark as outlined paths. No font dependency at render time — the SVG renders identically on a machine that's never seen Inter Tight. - Derived lockups. The trace script then embeds the mark path into the three standard lockups — symbol-only, navy-squircle layered mark, full layered logo above the wordmark — and writes them all to
apps/web/public/brand/. - Mac app asset. The same mark SVG is copied into
Assets.xcassets/CommonComputeMark.imageset/withpreserves-vector-representationset so SwiftUI resamples at every render scale instead of caching a single raster.
When we'll lend our brand, and when we won't.
Listings, integration pages, and editorial coverage are free to use the logo without asking. For any context where our logo appears next to a partner's wordmark — co-marketing, joint case studies, conference materials — drop a note to [email protected] and we'll sign off in a business day.