XERJ has no illustrated logotype. The logo is the word — and two 1 px rules that carry the story of the product. A paper-coloured line under XERJ — the row in storage. A yellow line over .AI — the indexed value served back as intelligence. Each rule is the colour of the text it connects to. The offset between them is deliberate: storage is the input, AI is the output, the wordmark is the transformation in between.
The brand is made of three decisions and nothing else: a single gold accent, a 1 px stroke, and typography doing the work a chart would do. Each has a reason. None is decoration.
Every industry that has a reference calls it the gold standard. A gold bar is 99.99 % pure by defined assay. A gold medal is the winner. A gold seal is notarised truth. The word holds across centuries — the Roman solidus, the Arabic dinar, gold leaf on Qur'anic manuscripts, gold trim on a thobe, gold on any document that has to still mean something ten years later. Gold earned the name because gold does not tarnish.
XERJ takes its name from the Arabic word for life — ḥayāh (حياة). In that tradition, gold carries weight beyond wealth. A gift of gold marks a milestone. Gold thread marks craft meant to outlast the wearer. Gold ink on parchment marks a truth the writer was willing to sign. Across all of it, gold is applied only to things already good enough to carry its weight. Success, not material.
We use the accent (#FFC400) the same way. It marks the one number a chart is about, the one word a sentence is pointing to, the p95 that says we are shipping. If a designer paints a row heading yellow because it "looks nice", they have devalued the stamp for the thing that actually deserves it.
Any modern screen can render a 1 px line. Most brands do not trust that to be enough. They add a gradient to give it depth. They add a shadow to give it weight. They widen it to 2 px "for emphasis". Each addition is a concession that the idea underneath was not strong enough to carry the line alone.
Our rule is absolute. Every hairline, every axis tick, every divider, every border, every bar in every chart: one pixel. Never wider. Never gradient. Never feathered. If a design needs a thicker stroke to be legible, the design has a bigger problem that the thicker stroke is covering up. Fix the idea, not the border.
This is engineering discipline, not aesthetic minimalism. Engineers do not ship a thousand lines of code when ten will do. Designers who have lived inside production systems do not ship 3 px borders when 1 px is sufficient. The narrowest line that still carries the information is the correct line.
An AI system outputs text. A log line is text. A query plan is text. A vector is a sequence of numbers rendered as text. A retrieval result is a snippet of text ranked against other snippets of text. The entire observable surface of a language model — prompt, response, embedding, audit trail — is plain text.
Marketing designers usually translate that text into pictures: illustrations, flowcharts, isometric servers with tiny humans standing next to them. Every translation loses fidelity. A query result drawn as a generic "document" icon tells you nothing; the same result as monospaced JSON tells you everything.
We do the opposite. Our dashboards are tables with good typographic taste. Our charts are 1 px strokes over a typographic axis. Our marketing pages render the same numbers our customers see on their consoles, at the same precision, without stylisation. Type is the native format of an AI system. Any other format is a translation away from the truth. Typography is not a substitute for an infographic — it is the infographic.
The block below is a product dashboard fragment rendered only with the rules above. No icon, no fill, no gradient. One gold stamp per row — exactly where the reader is meant to look.
Six numbers, six gold stamps, six 1 px dividers, zero decoration. Everything you need to know about the product is already here. That is the argument.
The mark is a two-stroke diagram of the product. The paper rule connects to XERJ from below — the storage layer, the rows on disk, the segment on the WAL. The yellow rule connects to .AI from above — the answer the agent reads back, the retrieval, the ranked vector. Each line is the colour of the half it anchors. They meet at the . — the exact boundary between stored bytes and served intelligence.
Alignment is measured from the baseline (y=170) and cap-top (y=70), not from the EM box — so the gap between each rule and its text is exactly 30 px at every scale. No optical nudging, no "looks right to me". Geometry wins.
The primary lockup. The root word is set in paper (#F4F2EC) on night (#0B0B0D). The suffix .AI takes the accent (#FFC400). This is the only place where accent is applied to a character inside the wordmark — the short form XERJ is never coloured.
Rule of colour: a rule is always the colour of the text it touches. The paper line under XERJ is paper (#F4F2EC); the yellow line over .AI is yellow (#FFC400). Never cross-colour. Never extend one rule to touch the other half of the word. Each rule owns exactly its half of the record.
When space is tight — app title bars, compact headers, system tray — the short form XERJ is used without the .AI suffix. At favicon scale only a single X remains. The letter mark is the only glyph the brand can be reduced to.
When the .AI drops off, the rule system simplifies: both rules take the colour of whatever's left. Short form = XERJ + two paper rules. Letter mark = X + two yellow rules. Single-colour, symmetric, same 30 px gap above and below.
The system line is the tiny, tracked-out, monospaced signature used on footers, dashboards, PDF page headers, and email signatures. It is set in IBM Plex Sans 600 at 13 px with 0.24 em tracking and a middle dot separator. Never substitute it for the wordmark on covers, heroes, or product splashes — it is deliberately quieter.
Approved second-tag variants: OBSERVE (default) · INDEX (docs) · EXPLAIN (compliance surfaces) · QUERY (product dashboards). One tag per surface, never stacked.
The wordmark exists in three treatments — night (primary), day (courtesy), and mono (for places we don't control, like a customer's slide deck or a partner's press release). The mono treatment keeps the .AI suffix but drops the accent colour, because we don't ship neon yellow on someone else's background.
The minimum padding around the wordmark on every side is equal to the cap height of the letter X at whatever size the mark is rendered. This rule is absolute — no edge of the wordmark ever sits closer than one X to a container border, a photo crop, another logo, or an interface chrome element.
Every surface has a pre-approved size. Below the minimum the wordmark is replaced by the short form, then by the letter mark, then it is removed entirely. The mark is never rendered below 16 px cap height — below that it becomes unreadable and damages the brand.
Both rules are drawn at a fixed 1 px weight regardless of wordmark size. Below 56 px the rules start to compete with the letterforms visually, so they drop off entirely — the wordmark stands on its typography alone from the nav bar down.
The two rules that carry the wordmark — 1 px and typography — are not decoration specific to a logo page. They are the same rules the product uses to render data. An AI data company that cannot show a chart cleanly cannot sell storage cleanly either. The sections below are live primitives, pulled from the same vocabulary that ships in the playground dashboards. Each one is a rule applied to information.
A headline number and an inline 1 px sparkline that answers where is it heading before the reader even finishes the word. No axis, no labels, no grid — the shape is the annotation. If the trend is down, the line goes down. No further interpretation required.
A full-width time line. One 1 px stroke across the whole panel. Minimum, peak and endpoints are called out underneath the curve — never floating over it, never inside a rounded tag. The chart is the line; the numbers are the legend.
A ranked list with aligned 1 px bars. Replaces the horizontal-bar chart entirely because a ranked list is a horizontal-bar chart — with the label, the value, and the percentage already in place. The bar just shows relative weight at a glance.
A single horizontal 1 px line broken into segments by stroke-opacity. Replaces the pie chart and the donut. Each segment is labelled below with its exact count and share — no legend floats over the bar, no colour is required to tell the parts apart. Weight does the job.
A grid of numbers whose text opacity encodes magnitude. The data is the visualisation — there are no cells, no boxes, no colour bands. Dark numbers are low. Bright numbers are high. The reader still sees the exact value, so the chart and the table are the same object.
A single value on a bounded 1 px track. The stroke fills from zero to the current reading; the remainder stays at low opacity. One line, two values (min and max), one headline. The fastest way to render how close is it to breaching? without lighting up a dashboard in traffic-light colours.
A grid of tiny labelled sparklines — one per dimension. Replaces the "eight separate line charts stacked in a row" anti-pattern. Each cell is a headline, a latest value, and a shape. The reader scans for the one that broke ranks.
Vertical 1 px lines. One line per bucket. No fills, no outlines, no caps — a bar is a stroke from baseline to value. When the data is ordinal (hours of day, day of week, bucket index), this is the right shape.
X/Y cloud rendered as · characters. The only chart in the system that has "point markers" — because the character is the datum. No filled circles, no open rings, no shapes encoding a third dimension. Just dots.
Multiple rows, each a DIST on its own line. The opacity carries the segment identity, the lengths carry the share. No stacked-bar colour salad, no legend wrapping under the chart.
Not a treemap in the D3 sense — no packed rectangles, no colour-fills. An indented ranked list where each row has a label, a value, a 1 px bar, and a share. Replaces sunbursts and boxed treemaps because the outline of the hierarchy is the visualisation.
The most honest chart an AI data company can ship — just the tail of the log. Time, severity, message. Errors take the gold accent because error is the word a page is most pointing at. Everything else stays in ink or mute.
The charts below are the ones specific to AI workloads — embeddings, retrieval flows, token budgets, multi-dim runs, attention. They are not a different design language. Same 1 px rule, same typography, same stamp of gold only on the thing the reader is meant to look at.
The iconic AI picture. A 2 D UMAP projection of high-dimensional embeddings, with 1 px convex hulls around each cluster and centroid labels sitting outside the cloud. Dots are · characters; the gold crosshair is the current query's projected embedding. No kmeans fuzz, no colour palette.
Flow between two ordered sets — queries on the left, retrieved chunks on the right, one 1 px Bézier arc per retrieval. Arc opacity is the relevance score. Replaces the Sankey diagram for RAG pipelines because a Sankey wastes ninety percent of its ink on colour-coded ribbons; we only need the line.
A single horizontal strip split into segments, each labelled directly beneath. The natural home for token budgets, context window breakdowns, and cost attribution. Replaces funnels and waterfalls with one honest line.
N axes, N dimensions, one 1 px polyline per row. Accumulated opacity makes density where many rows converge — the shape of the data across five or six variables at once. The gold line is a single highlighted run, so the reader can see where it falls in the cloud.
The paragraph is the chart. Every token's opacity equals its attention weight; the peak tokens cross into the gold accent. For a RAG system this is the cleanest possible answer to which tokens actually mattered. No heatmap overlay, no coloured highlights — just type rendered at the weight the model assigned.
Seventeen primitives above, one rule across all of them: every chart is a 1 px stroke, a number, or an opacity applied to a character. No fills, no colour bands, no icons on axes, no legends floating over curves. The general six handle the metrics a platform page usually needs; the next six cover ordinal bars, scatter, stacked, treemaps and event streams; the last five are the AI set — embedding clusters, retrieval connectivity, token allocation, multi-dim runs, attention. The storage is for the chart; the chart is the storage; the rules are the same line.
Every asset ships as SVG. We do not publish PNG or JPG variants because a raster of the wordmark is either wrong size or wrong compression — and both of those are easier to fix upstream by using the SVG. If a partner's CMS cannot render SVG, the answer is to upgrade the CMS, not to raster the logo. The full brandbook is available as a print-ready PDF below.
TYPE IS THE UI.
1 PX IS THE STANDARD.
GOLD IS EARNED.
XERJ.AI · OBSERVE
END OF BRAND BOOK · 17 CHART PRIMITIVES · 14 DO/DON'T RULES · 7 DOWNLOADS
