Brand guidelines · v1.0 · August 2026

The Proof IT brand

Everything needed to produce something that looks like Proof IT — the mark, the palette, the type, the spacing, the components and the way we write. Built from the live design system behind this site, so what you see here is what actually ships.

01 — Basics

Who we are, in the words we actually use

Proof IT is a European software engineering company, founded in Riga in 2004. We build a full-cycle core insurance platform (PINS), a family of named AI products, and custom software for regulated industries. ISO 27001 and ISO 9001 certified.

Name

Proof IT — two words, capital I and T — in all running text, legal documents and press. PROOFIT set solid is the logo only, never body copy. Legal entity: Proof IT SIA. Do not write “ProofIT”, “Proof-IT” or “proofit” outside of URLs and email addresses.

Tagline

Simplifying the future through code. Used in the hero, the logo lockup and presentation title slides. Sentence case, full stop only when it ends a sentence. Never translated in marketing assets.

Descriptor

Insurance technology & enterprise AI. The one-line descriptor for social images, banners and stands, where the tagline is too abstract to explain the business.

Boilerplate

Short — 1 sentence

Proof IT is a European software engineering company building core insurance platforms, enterprise AI products and custom software for regulated industries.

Long — press / partner decks

Founded in Riga in 2004, Proof IT is a European software engineering company of around 100 engineers. It delivers PINS — a full-cycle core insurance platform — a family of named AI products for voice, documents and customer operations, and custom engineering for regulated industries. Proof IT is certified to ISO/IEC 27001 and ISO 9001 and holds a Latvian Industrial Security Certificate.

Three engineering directions

Everything we sell falls under one of three directions. Each one owns an accent colour, and that colour is the only signal of direction anywhere in the brand — in cards, charts, slides and diagrams.

Insurance

PINS core platform, broker and fleet portals, TPA control layer, claims automation. Accent: brand blue.

AI products

SARA, MailFlow, VoiceConnect, CommsHub, Ingredivo, MCP server, agent layer. Accent: signal green.

Custom engineering

Legacy modernisation, bespoke platforms, integration work for regulated industries. Accent: violet.

03 — Colour

A quiet base, three loud accents

The palette is almost entirely neutral. Colour carries meaning: blue is insurance, green is AI, violet is custom engineering. If something on a page is coloured, it is because it belongs to one of those three — never for decoration. Click any swatch to copy its hex.

Brand core
Direction accents
Interface neutrals
TokenDark themeLight themeUsed for
--bg#0A0B0D#FAFAFBPage background
--bg-elev#131418#FFFFFFFooter, raised panels
--bg-card#16181D#FFFFFFCards, tiles
--bg-card-hover#1C1F25#F5F6F8Card hover state
--border#25272D#E6E7EBDefault 1 px hairline
--border-strong#34373F#D3D5DBHover, ghost buttons, dividers
--text#ECECEF#0A0B0DHeadlines, primary copy
--text-dim#9CA0AA#4D5159Body copy, descriptions
--text-muted#6B6F78#7A7E87Labels, captions, eyebrows
Rules
Do
  • Pick the accent by direction, not by taste.
  • Use the light-theme accent values on white — the dark-theme ones fail contrast there.
  • Keep large surfaces neutral; accents stay under roughly 10 % of any layout.
  • Body text must clear WCAG AA (4.5:1) against its background in both themes.
Don’t
  • Mix two accents in one component — a card is blue or green, never both.
  • Introduce new colours for charts; use tints of the direction accent instead.
  • Set green text on white at small sizes without switching to the light-theme value.
  • Use brand navy as a page background on the web — it belongs to the icon and social images.
04 — Typography

Inter for everything, mono for the machine parts

Primary — Inter

Headlines, body, UI, print. Weights 400 / 500 / 600 / 700 for text, 900 reserved for the logo. Headlines are set at weight 500 with negative tracking — the restraint is deliberate; we do not shout in bold.

Free, open-source (SIL Open Font License). Office fallback: Segoe UI, then Arial.

Secondary — JetBrains Mono

Eyebrows, labels, table headers, contacts, version stamps, code and anything that should read as machine output. Weights 400 / 500 only, uppercase, tracking +0.15em at label sizes.

Free, open-source (SIL Open Font License). Fallback: any system monospace.

Weights
Regular400 — body
Medium500 — headlines, buttons
Semibold600 — card titles
Bold700 — emphasis, rare
Black900 — logo only
Type scale
H1 · page title · clamp(40 → 72 px) · 500 · −0.03em · 1.02
Simplifying the future through code
H2 · section title · clamp(28 → 42 px) · 500 · −0.02em · 1.1
A core platform, not a patchwork
H3 · card title · 20 px · 600 · −0.01em
Claims automation
Lead · 18 px · 400 · text-dim · max 60ch
European software engineering: full-cycle insurance platform PINS, named AI products, and custom engineering for regulated industries.
Body · 14 px · 400 · text-dim · line-height 1.55
Every module ships with an audit trail, role-based access and an API contract that survives the next core migration. That is the whole product philosophy in one sentence.
Small · 13 px · navigation, footer links, card body
Security & Compliance · ISO 27001 / 9001 · SLA & Support
Micro · JetBrains Mono · 11 px · uppercase · +0.15em
02 — Insurance platform
Rules
Do
  • Cap headline width at ~16 characters, lead paragraphs at ~60.
  • Keep negative tracking on large type; leave small type at default.
  • Use sentence case everywhere except mono labels, which are uppercase.
  • Let headlines wrap naturally — no manual line breaks in responsive layouts.
Don’t
  • Set headlines in weight 700 or 900 — that reads as a different brand.
  • Use Inter Black anywhere but the logo.
  • Use mono for body copy or anything longer than a short label.
  • Go below 11 px for anything a customer has to read.
05 — Layout & space

1280 wide, 14 px corners, one hairline

Container

Max width 1280 px, centred, side padding 32 px20 px below 768 px.

Section rhythm

Vertical padding 60 px (44 px for tight sections), separated by a single 1 px border, never by a background change.

Grid

Cards sit on a 12–16 px gap grid: three columns on desktop, two on tablet, one below 640 px.

Spacing scale
6
8
12
16
24
28
32
44
60
80
Corner radii
6 — chips
8 — inputs
10 — buttons
12 — small cards
14 — default card
16 — large panels
100 — pills
Depth

Elevation

One shadow only, and only on genuinely floating elements (modals, hovering feature cards):
dark — 0 20px 60px rgba(0,0,0,.4)
light — 0 12px 40px rgba(15,18,25,.06)

Everything else separates with a 1 px border. Flat is the default.

Background field

A fixed 64 × 64 px grid at 2.5 % white (dark) / 4 % black (light), plus one blurred radial glow in the AI accent behind the hero. Both are decoration — never place content that depends on them.

06 — Components

The pieces every page is built from

These are live elements from the site’s stylesheet, not screenshots. Toggle the theme in the navigation to see how each behaves.

Buttons

Primary

Inverse fill, 10 px radius, 12/24 padding, 14 px medium, trailing ↗. One per view.

Ghost

Transparent with a strong border. Secondary paths — documentation, comparisons.

Nav CTA

Pill in the navigation bar. Reserved for “Contact”.

Chips and labels
Policy administration Claims automation Document AI Voice agents Legacy modernisation
Cards

Insurance

PINS core platform

Policy, claims, billing and partner portals on one data model, deployed in the customer’s cloud or ours.

AI product

MailFlow

Reads incoming mail, classifies it, extracts the data and files it where the process expects it.

Custom

Legacy modernisation

Strangler-pattern replacement of core systems that cannot go offline.

Section header
04 — Security

Certified, audited, and boring on purpose

Every section opens the same way: a mono eyebrow with a number and a short label, then one headline of no more than about 22 characters per line.

Trust badges

ISO/IEC 27001

Information security management — certified.

ISO 9001

Quality management — certified.

Industrial Security

Certificate of the Republic of Latvia.

07 — Imagery & icons

Diagrams over stock photography

We sell engineering, so we show engineering: architecture diagrams, product interfaces, real people. Stock imagery of handshakes, glowing brains, robots and blue circuit boards is off-brand and never appears in our materials.

Social / OG images

1200 × 630 px, brand navy field with the 64 px grid, wordmark at the left, descriptor beneath, credential line at the bottom. One per major page.

Diagrams

1 px borders, 14 px radii, mono labels, direction accents for flows. Same palette as the interface — a diagram should look like it was cut out of the product.

Icons

Line icons on a 24 px grid, 1.5 px stroke, round caps, no fills. Text-dim by default, direction accent when the icon carries meaning.

Photography

People at work in natural light, no heavy grading. Faces stay recognisable; office shots stay unstaged.

Screenshots

Real product, anonymised data, cropped to what the sentence claims. 14 px radius and a 1 px border, never a browser chrome mockup.

EU funding marks

Supplied by the funding programme and never restyled, recoloured or cropped. They keep their own clear space in the footer strip.

08 — Voice & tone

Precise, calm, unimpressed by its own technology

Our readers are insurers, TPAs, brokers and IT leads in regulated industries. They are sceptical by profession. We write for someone who will check the claim — short sentences, concrete numbers, no adjectives doing the work of evidence.

We write
  • “Policy, claims and billing on one data model.”
  • “Certified to ISO 27001 and ISO 9001 since 2004.”
  • “Runs in your cloud or ours.”
  • British spelling, sentence case, Oxford comma optional but consistent.
  • Active voice, present tense, second person for the reader.
We don’t write
  • “Revolutionary, cutting-edge, next-generation AI-powered synergy.”
  • “Transform your business!” — exclamation marks, ever.
  • Claims without a number, a certificate or a customer behind them.
  • Jargon the buyer would have to look up, unless we define it in the same sentence.
  • “Solutions” as a stand-in for whatever we are actually selling.
Product naming
Written asWhat it isNote
PINSCore insurance platformAll caps, never “Pins”
SARAAI assistantAll caps
MailFlowDocument and mail AICamelCase, one word
VoiceConnectVoice AICamelCase, one word
CommsHubCommunications hubCamelCase, one word
ClaimMailClaims correspondence AICamelCase, one word
IngredivoProduct-data AITitle case

Product names never take the company name as a prefix in body copy — write “PINS”, not “Proof IT PINS”, once the company has been introduced.

09 — Downloads

Files, and the rule that comes with them

Vector master files. Use them as supplied. If a format you need is missing, ask proofit@proofit.digital rather than rebuilding the mark yourself.

The SVG wordmarks reference the Inter typeface rather than converted outlines. They render correctly on the web and in any application with Inter installed. Outlined SVG and print-ready PDF versions are the next item on the list — see below.
10 — Open items

Known gaps, tracked honestly

A brand book that hides its loose ends stops being useful. These are the decisions and files still outstanding as of v1.0.