The SealGate brand system.
The source of truth for our logo, color, typography, and voice. Precise, systemic, always on — like the product.
The gate and the seal.
Two parts, one mark. The frame is the gate: a rounded square with a solid tag anchored to the top-left corner, the Hackbox motif at logo scale. Inside it sits the seal, a serif “S” rebuilt out of rounded pixel runs, with a small tick tucked into the opposite corner. In the wordmark the gate stands in for the S, set a stem’s width from the E so SEALGATE reads as one word.
Primary lockup — cyan seal, white type, on black
Construction
The seal is drawn on a grid two units tall for every one wide, and every run is a rounded bar sitting on it. It sits centred in a 1:1 gate, and the corner tick tucks in beneath the S rather than sitting beside it, which is what keeps the gate square.
Every file on this page is generated from one master drawing, so the colorways can never drift apart. Take the supplied file and recolor it if you need a variant we do not ship. Do not redraw the mark.
Logomark
Core Cyan
White
Graphene Grey
Black
Wordmark variants
Cyan mark, grey type
All white (mono)
All Core Cyan (mono)
All black, on light
Icon
For the places that will not take a landscape mark: app icons, social avatars, anything that crops to a circle. Core Cyan is the default, and the only tile that stays legible against both a light and a dark browser chrome.
Core Cyan (default)
Black tile
Black tile, white mark
No tile
Clearspace
Keep margin equal to the tag's depth on all sides. Nothing intrudes.
Minimum size
Logomark 20 px tall; wordmark 160 px wide.
Do
- Use Core Cyan on black as the default.
- Knock out to black on cyan or white fields.
- Keep the tag anchored to the top-left corner.
- Leave a stem's width between the gate and the E.
Don't
- Recolor outside black, white, or Core Cyan.
- Add gradients, shadows, or glows.
- Stretch, skew, or rotate the geometry.
- Tuck the E behind the gate or clip it to fit.
A monochrome system with one signal.
Black and grey carry the surface; Core Cyan is the single signal, used sparingly. Treat the usage shares below as a hard budget.
Baseline Black
#000000
Backgrounds
Graphene Grey
#9BA4A6
Secondary text, UI
Core Cyan
#C3FFFD
Accent, the signal
Wavelength White
#F9F9F9
Primary text
Usage budget
Extended palette
Accents for states and data. Circuit Green and Infra Red are functional only: success and danger. Keep them out of decoration.
Grid Grey
Core Cyan
Graphene Grey
Circuit Green
Infra Red
Do
- Build on black; let negative space dominate.
- Reserve Core Cyan for the one thing you want seen.
- Use green and red only for success and danger.
- Pair white text with black backgrounds.
Don't
- Flood a surface in cyan.
- Add off-brand hues for accents or charts.
- Use red or green as decoration.
- Put Core Cyan text on white.
Archivo for voice, JetBrains Mono for data.
Archivo carries every headline and paragraph, set light and tight. JetBrains Mono handles code, data, and system labels.
Aa
ABCDEFGHIJKLM
abcdefghijklm 0123456789
Aa
ABCDEFGHIJKLM
abcdefghijklm 0123456789
Type scale
Control how agents access your data
Stop data leaks before they happen
Enforce policy at the tool-call level
Every tool call. Every data flow.
SealGate sits between any agent and your data sources, enforcing policy deterministically at the tool-call level.
Monitor AI agent sessions in real time.
Do
- Set large headlines in Archivo Light (300).
- Use JetBrains Mono for code, hex, labels, and metrics.
- Keep body copy in Archivo Regular.
- Let weight and size carry the hierarchy.
Don't
- Swap in another sans (Inter, Helvetica, system-ui).
- Set prose in the monospace face.
- Use heavy bold weights for display headlines.
- Stack too many weights in one block.
Precise, technical, and certain.
We talk to people who carry real security risk. Lead with the mechanism and the stakes; never reach for hype.
Write deterministically
SealGate enforces, blocks, and records. Use that definite register and drop hedges like 'helps reduce' or 'aims to'.
Plain about risk
Name the threat directly: data leaks, exfiltration, the lethal trifecta. Don't soften or bury it.
Technical and legible
Use the real terms (MCP, tool calls, runtime, SIEM) but keep sentences clean enough to follow.
Confident and plain
No 'revolutionary', no 'next-gen', no exclamation marks. Let precision do the convincing.
In practice
On voice
“SealGate intercepts the lethal trifecta and halts the action for review before exfiltration happens.”
Off voice
“SealGate's revolutionary AI helps keep your data safer than ever before!”
On voice
“Every tool call is logged to the employee whose authority the agent acted under.”
Off voice
“Get total peace of mind with best-in-class, next-gen agent observability.”
Do
- Lead with what SealGate does and the risk it removes.
- Use definite verbs: enforces, blocks, records, intercepts.
- Name real threats and systems by their actual names.
- Keep sentences tight.
Don't
- Reach for hype: revolutionary, game-changing, next-gen.
- Hedge with 'helps', 'aims to', or 'should'.
- Use exclamation marks or salesy enthusiasm.
- Bury the stakes in vague abstraction.
The Hackbox: our structural motif.
One modular unit: a cyan wireframe square — the Box — tagged with a solid cyan rectangle. The logomark is this unit at its smallest, with the seal inside it. Scale by duplicating the box across a grid.
The Box
A 1:1 square, wireframe only, 2 px Core Cyan stroke. No fill.
The Tag — the 40 / 10 rule
A solid cyan rectangle, 40% wide and 10% tall, anchored flush to a corner. Never floating.
Rhythm
Vary tag corners across a cluster to create movement.
Do
- Build 1:1 squares, 2px cyan stroke, no fill.
- Size every tag 40% × 10%, anchored to a corner.
- Duplicate boxes on a grid.
- Alternate tag corners for rhythm.
Don't
- Let a tag float free of the box edge.
- Fill the box or use a 1px stroke.
- Stretch a single box to fill space.
- Break the 40/10 ratio or place tags mid-edge.
Build it like it's
always on.
Questions, or need source assets? Reach the team.