The mark, the palette, and what we say

It's a cloud with a lock in it, and the reading is the whole company: infrastructure you hold rather than rent. It came from the repatriation work and it still fits the silicon work, because both are arguments about owning the thing you depend on.

Datacenter.Dev

• Keep clear space around it of at least the height of the lock. It's a dense mark and it closes up when crowded.
• Do not recolor it, outline it, add a shadow, or place it on a busy photograph. On a light ground use it as is; it was drawn to survive both.
• The wordmark is Geist Mono, bold, with the dot. It's Datacenter.Dev, a capital on each half, never DataCenter.dev and never DATACENTER.DEV.
• The address is not the name. In a URL or an email it stays lowercase, because datacenter.dev there is a string a machine matches exactly rather than a word a reader sees. Write Datacenter.Dev in a sentence and [email protected]in an address, on the same page, without treating it as an inconsistency.

Two faces, both Geist. Geist Sans sets everything a person reads as prose. Geist Mono sets anything that is a value, a label, a result or a piece of code, which is what makes a measurement look like a measurement.

Uppercase is never set below 17px anywhere, in any medium. Capitals lose their letterforms at small sizes and the site would rather drop a label than set an unreadable one.

These are technical terms, most of them with an existing meaning in the literature, and the quickest way to misrepresent us is to use one of them loosely. Where a term's plain reading claims more than we do, the limit is printed with it and travels with it.

• Supercompiler

  The product, and the algorithm it's named for. As a pipeline it compiles to silicon: it places computation onto a dataflow fabric and emits a machine checkable argument that the placement preserves the semantics of the reference implementation. As an algorithm it's one optimization rather than a pass pipeline, subsuming constant folding, propagation, dead code elimination, deforestation and partial evaluation by driving the program symbolically one step at a time, folding when it meets a configuration it has seen before, and generalizing when it detects a homeomorphic embedding. That is the mechanism behind collapsing an algorithm rather than merely emitting faster code for it.

  Bounds. Driving is ahead of time only. It has unbounded cost, so it's deliberately excluded from the run path, and no figure measured at run time is attributable to it. The name now covers the whole pipeline, so this bound has to be stated where a run time figure is published rather than assumed from the word.

  Not a synonym for optimizer, and not a synonym for high level synthesis, which does not emit the proof. A supercompiler is a specific technique from the partial evaluation literature, due to Turchin. Naming the product for it claims that the technique is what the product does, not a borrowed label.

• The Verification Wall

  A limit on what testing can establish in principle, no matter how much testing is bought.

  Not the verification gap, which is a throughput problem and does respond to more engineers and better tooling. The two are routinely conflated and the distinction is the whole point of the term.

• Scope

  What a figure is a measurement of. Every number on this site travels with the unit it was taken on, so a reader sizes it correctly.

Everything above, as it ships. The mark is a large PNG because it's meant to be scaled down rather than up; for anything under 64px use the favicon instead.

• The markPNG with transparency, 2190 by 1920Download
• The mark, vectorSVG, one path, scales to any sizeDownload
• FaviconPNG, 32 by 32Download
• Touch iconPNG, for iOS home screensDownload
• Social cardPNG, 2400 by 1260, for link previewsDownload