Brand Guidelines

Standard
Compute Brand Book — Identity & Guidelines

Version
2.0
Updated
February 2026
Classification
Internal
01 Brand Story 02 Logo System 03 Color System 04 Typography 05 Spacing & Grid 06 Motion 07 Voice & Tone 08 Usage Guidelines

Infrastructure
for what matters.

Standard Compute builds the foundational compute layer that companies depend on when reliability isn't optional — it's the product. We believe infrastructure should disappear into the background: invisible when it works, indispensable by design.

Our brand reflects this philosophy. It is engineered, restrained, and precise — a visual system that communicates trustworthiness through structure rather than ornamentation. Every element is deliberate. Nothing is decorative.

Mission

Make compute infrastructure so reliable it becomes invisible.

Values

Precision over decoration. Clarity over cleverness. Substance over spectacle. Reliability as a first principle.

Positioning

The compute standard that teams trust when uptime defines their product.

Monochrome-first.
Color with purpose.

Our palette is 80% monochrome, 20% functional color. All values are defined in OKLCH for perceptual consistency across light and dark themes. The primary hue — Compute Blue (220°) — is reserved for interactive elements, focus states, and key actions.

Neutral Scale
500.985
1000.97
2000.90
3000.82
4000.70
5000.58
6000.45
7000.35
8000.25
9000.18
9500.13
Black0.08
Primary — Compute Blue (Hue 220°)
500.02C
1000.04C
2000.07C
3000.11C
4000.14C
5000.15C
6000.14C
7000.12C
8000.09C
9000.06C
Status Colors
Success
Green 145°
Warning
Amber 75°
Error
Red 25°
Info
Blue 250°
Color Ratio — 80/20 Rule
80% MONO
20% COLOR

DM Sans + DM Mono

Our type system pairs DM Sans for interface and editorial text with DM Mono for data, code, and system labels. Both share the same underlying geometry, ensuring visual cohesion across contexts.

The infrastructure
you don't think about.
Built for teams that can't afford to think about infrastructure. Standard Compute provides the reliable, scalable compute layer that powers mission-critical applications.
Display48 / 700-0.04em
Standard Compute
Heading 136 / 700-0.03em
Infrastructure layer
Heading 228 / 700-0.025em
Compute at every scale
Heading 320 / 600-0.015em
Reliability as a first principle
Body16 / 4000
Deploy, scale, and manage compute.
Small14 / 4000
Region: us-east-1 · Status: Operational
Caption12 / 5000.02em
Last updated 2 minutes ago
Mono13 / 4000.02em
std-compute --deploy --region us-east-1

4px base scale

All spacing derives from a 4px base unit. This ensures consistent vertical rhythm and predictable alignment across all components and breakpoints. The layout uses a 24-column fluid grid.

sp-1
4px
sp-2
8px
sp-3
12px
sp-4
16px
sp-6
24px
sp-8
32px
sp-10
40px
sp-12
48px
sp-16
64px
sp-20
80px
sp-24
96px
sp-32
128px
Grid System

24-column fluid grid with 24px gutters. Max content width: 1120px. Side margins collapse to 24px on mobile. Columns snap to 12/8/6/4 on responsive breakpoints.

Border Radius
6px
10px
16px

Easing & Duration

Motion should feel mechanical and precise — like well-engineered hardware. Favor ease-out for entrances and spring curves for interactive feedback. Keep durations tight: 150–400ms for UI, up to 600ms for page transitions.

Ease Out
Entrances & reveals
cubic-bezier(0, 0, 0.2, 1)
Ease In-Out
State transitions
cubic-bezier(0.4, 0, 0.2, 1)
Spring
Interactive feedback
cubic-bezier(0.34, 1.56, 0.64, 1)
Micro
150ms
Hover, focus, toggle
Standard
300ms
Expand, collapse, slide
Page
600ms
Route, reveal, orchestrate

How we speak

Standard Compute speaks with the confidence of an engineer and the clarity of great documentation. We are precise, calm, and direct — never performative, never vague.

Precise

Say exactly what you mean. Avoid hedge words, filler, and unnecessary qualifiers. If something takes 12ms, say 12ms — not "blazing fast." Numbers build trust; adjectives erode it.

Technical, not jargony

Use the correct technical term, but always in service of clarity. Don't simplify to the point of inaccuracy, and don't complicate to signal expertise. Write for the senior engineer at 11pm reviewing a production incident.

Calm under pressure

Infrastructure failures are stressful. Our communication should reduce stress, not amplify it. Status updates are factual. Incident reports are clear. Error messages point to resolution, never blame.

Restrained confidence

We don't say "world-class" or "cutting-edge." We describe what we built, show what it does, and let the work speak. Confidence is in the structure, not the superlatives.

Writing examples
Do

"Deploy to 12 regions in under 4 seconds. Zero cold starts."

Don't

"Lightning-fast global deployment at unprecedented scale!"

Correct usage

These guidelines protect the integrity of the Standard Compute brand. When in doubt, refer to this document or contact the brand team.

StandardCompute
StandardCompute