Shared visual identity for nrds, YRSO, and Monmonmon. Click any swatch or code to copy.
This is the living style guide for nrds and its products, but it's more than a collection of colors and fonts. It codifies who we are, how we think, and why our products feel the way they do. The brand identity, the design philosophy, and the visual system are inseparable: every color choice traces back to a principle, every principle traces back to a belief about how security software should treat the people who use it.
Use it as the source of truth when building interfaces, writing copy, creating marketing material, or making any design decision. Start with the brand identity to understand the why, then let the rest follow. If it's not in here, it's not on brand.
Information security is stressful enough. Our products should never add to that stress. The core principle across everything we build is calm: interfaces that lower the heart rate, not raise it.
We take this idea from two traditions. From the Japanese concept of ma (間), the deliberate use of empty space not as absence, but as presence. A pause in music is still music. A margin around a paragraph is still part of the design. Space gives the eye somewhere to rest and the mind room to think. From Bauhaus functionalism, the conviction that every element must earn its place. If a button, a color, a line of text doesn't serve the person using it, it shouldn't exist.
Calm is not passive. It's a decision to show people only what they need, when they need it. Our products should feel like a conversation with someone competent and unhurried, not a control room with every alarm lit up.
This means: one action per screen where possible. Progressive disclosure over upfront complexity. Status communicated through color and tone, not exclamation marks. Error states that explain what happened and what to do next, not just what went wrong. Dashboards that surface the single thing that matters right now, rather than every metric that could theoretically matter.
Compliance doesn't need to look like a threat dashboard. Device security doesn't need to feel like surveillance. When someone opens YRSO or Monmonmon, the first feeling should be I'm in control, not I'm behind.
The palette draws from Japanese botanical ingredients (mochi, matcha, yuzu, azuki): warm, muted tones that feel more like a well-made notebook than enterprise software. A cream ground, ink-dark type, and color used sparingly to signal status, to guide attention, never for decoration.
All three brands share the same typographic system, color palette, and design principles. Each product has its own squircle mark, a single letter on a deep plum field, that identifies it within the family while keeping them visually connected.
Alongside the botanical palette sits a set of high-energy accents we call matsuri (祭), the Japanese word for festival. Where the core colors are quiet and grounding, the matsuri colors are loud, saturated, and unapologetic: dragonfruit, nami, yuzu electric, wasabi, koi, sakura UV. Think summer festival lanterns against a night sky. They exist for the moments that need to cut through: a hero CTA, a brand splash, a status that demands attention. Use them sparingly and they hit harder.
The governing company. nrds helps SaaS organisations get their information security in order, from first principles to full management system optimization. Consulting, implementation, and the products below all ship under this umbrella.
Compliance management platform for SaaS companies. YRSO turns ISO 27001, SOC 2, and GDPR obligations into manageable workflows: task management with deadline tracking, framework orchestration across multiple standards, and incident/case management for continuous improvement. One command center instead of scattered spreadsheets.
Privacy-first device security monitoring. Monmonmon performs read-only compliance checks (encryption, firewall, malware protection) without controlling devices or tracking users. No wiping, no software installation, no location or browsing data. Open-source agent, EU-hosted (Netherlands / France), GDPR-native. €1 per active device per month.
Three typefaces, each with a clear job. Outfit for display and headings: geometric, sturdy, with a quiet friendliness that keeps things approachable. DM Sans for body text: humanist proportions, readable at any size, comfortable over long stretches. System monospace for code, data, and terminal output, whatever the user's machine already trusts. No custom mono font to load, no fighting the OS.
The combination is functional without being cold, modern without being trendy. Typography carries the interface; decoration stays out of the way. When in doubt, let the type breathe. Generous line-height, restrained sizes, and enough negative space to let each word land.
Outfit is a geometric sans-serif from the Google Fonts library. We use it for headings, navigation labels, section titles, and anywhere text needs to signal structure rather than be read in long form. Its rounded terminals give it warmth without sacrificing clarity.
DM Sans is a low-contrast geometric sans-serif designed for comfortable reading at small sizes. We use it for body copy, descriptions, interface text, and anything meant to be read rather than scanned. Its humanist proportions keep long passages from feeling mechanical.
We don't ship a custom monospace font. Code, hex values, terminal output, and technical metadata all render in the system monospace stack: ui-monospace, SF Mono, SFMono-Regular, Menlo, monospace. This keeps load times fast, respects the user's environment, and ensures code always looks like code.
Named after the ume, the Japanese plum blossom that flowers in late winter, before anything else dares to. In Japanese culture it stands for resilience and quiet endurance. Plum is the darkest color in our palette, almost black but with a living warmth that pure black never has. It's the field our logo marks sit on, the foundation that everything else grows from. When you see plum, you're looking at the identity itself. Something that was here before you arrived and will be here after.
The color of sumi, the carbon ink used in Japanese calligraphy. Not black, but a deep blue-charcoal with just enough warmth to feel human. Ink is our primary text color and the backbone of every interface. Calligraphy ink rewards precision and intention; each stroke is deliberate. That's how we think about the words and interfaces we put in front of people: say what you mean, then stop.
Mochi is pounded rice cake: soft, slightly chewy, deceptively simple to look at but surprisingly involved to make well. The pink comes from sakura mochi, wrapped in a pickled cherry blossom leaf. It's our primary accent color: the warmth in what could otherwise be a cold, technical product. Security software doesn't have to look like a threat dashboard. Mochi says we take the work seriously without taking ourselves too seriously. When mochi needs to raise its voice, it becomes dragonfruit, the campaign color in our matsuri palette.
Matcha is stone-ground green tea, the centerpiece of the tea ceremony, where every gesture has purpose. The color is vegetal, alive, and calming. In our products, matcha means things are healthy: checks passing, systems compliant, status green. The deep variant doubles as our success color. Matcha reminds us that security isn't a crisis to manage. It's a practice to maintain, one deliberate step at a time, like whisking tea.
Yuzu is a Japanese citrus: intensely aromatic, tart, impossible to ignore when you encounter it. The color is a warm, honeyed gold. We use it for things that need attention without alarm: warnings, highlights, deadlines approaching, boolean values in terminal output. Yuzu is the gentle tap on the shoulder before matcha deep or azuki need to raise their voice. It says look here without saying panic.
Azuki is the red bean at the heart of Japanese sweets: earthy, grounding, a little bitter before the sweetness comes through. The color is a deep wine that sits between brown and crimson. We reach for azuki when something is serious: critical findings, destructive actions, things that deserve a moment of pause. It carries weight without being aggressive. Where mochi is warmth and matcha is health, azuki is gravity, the color that says this matters, pay attention.
The festival colors: high-energy accents for moments that need to cut through. Each matsuri color is the loud counterpart of a botanical: dragonfruit for mochi, nami for ink, yuzu electric for yuzu, wasabi for matcha, torii for azuki, sakura UV for plum. When the calm palette needs to raise its voice, these are the ones that step in.
How the specials work together and with the core palette. Shown on dark and light backgrounds with sample button treatments.
Reusable patterns for communicating status, alerts, and confirmations. All colors come from the existing palette.
Modals use a fog overlay with backdrop-filter: blur(2px) over ink at 25% opacity. The card pops in with a spring animation.
Your organisation has 14 active risk assessments across 3 departments. The next review cycle begins on 1 April 2026.
This will notify all assigned reviewers and lock the assessment for editing until the review is complete.
42 controls mapped across ISO 27001 Annex A. 3 custom controls added by your team.
This will permanently remove A.8.2 - Information Classification and all associated evidence. This action cannot be undone.
/* Fog overlay */ .fog { position: fixed; inset: 0; background: rgba(26,26,46,0.25); backdrop-filter: blur(2px); z-index: 40; } /* Modal card */ .modal { position: fixed; top: 50%; left: 50%; transform: translate(-50%, -50%); background: white; border-radius: 16px; box-shadow: 0 25px 50px rgba(26,26,46,0.15); z-index: 55; } /* Pop-in animation */ @keyframes modal-pop { 0% { opacity: 0; transform: translate(-50%,-50%) scale(.92); } 60% { opacity: 1; transform: translate(-50%,-50%) scale(1.02); } 100% { opacity: 1; transform: translate(-50%,-50%) scale(1); } } .modal.active { animation: modal-pop .3s cubic-bezier(.34,1.4,.64,1) forwards; }
Compliance has a branding problem. On one end you get the enterprise monoliths (the IBMs, the Big Four) radiating authority through sheer mass: dark suits, navy palettes, stock photos of handshakes in glass boardrooms. On the other end you get the VC-funded SaaS plays (the Vantas) radiating speed and automation: gradients, dashboards, "get compliant in weeks" urgency. Both are effective. Neither is us.
nrds is the calm professional in the room. The one who has read the standard cover to cover, understands the business context, and explains things in plain language without reaching for jargon or fear. We don't judge, we solve. When something is broken we fix it, understand why it broke, and make sure it doesn't happen again. The Japanese call this saihatsu bōshi (再発防止): prevention of recurrence. It's the engine behind our approach to continuous improvement and it runs through everything we build.
We are not selling authority or velocity. We are selling clarity.
This shapes every visual decision. The design language draws equally from two traditions that share a deep conviction: less, but better.
Ma (間): negative space is not empty, it is active. A page that breathes earns more trust than one that shouts.
Wabi-sabi (侘寂): beauty in restraint and imperfection. Muted tones over saturated ones. A colour palette named after kitchen ingredients, not corporate abstractions.
Kanso (簡素): elimination of clutter. If a UI element does not serve the person using it, remove it. We basically Marie Kondo compliance platforms. If it doesn't spark joy or pass an audit, it goes.
Form follows function. Every colour, every typeface, every spacing decision exists because it solves a problem, not because it looks good in a pitch deck.
Geometric clarity. Outfit for headings, DM Sans for body, system monospace for code. Three tools, each with a clear job. No decorative fonts.
Accessible to all. Design that works for the junior compliance officer reading their first audit report just as well as for the CISO reviewing a board summary.
The overlap between these traditions is the brand. Zen gives us the palette, the breathing room, the quiet confidence. Bauhaus gives us the grid, the type system, the functional rigour. Together they produce something that feels considered rather than designed: a tool that gets out of your way and lets you focus on the work that matters.
When in doubt, ask: would a calm, competent professional choose this? If the answer is yes, ship it. If it feels like it is trying to impress rather than inform, strip it back.
The visual identity operates in two registers. Most of the time it is quiet, grounded, and trustworthy: the botanical palette doing its job. But when a moment needs to land (a hero, a CTA, a campaign splash) it shifts into something louder. Understanding when to use which register is the single most important design decision you will make.
Mochi #d4577a is the colour people should associate with nrds. It appears in the logo treatment ("nerd as a service"), active navigation states, text links, emphasis, and anywhere the brand needs to be present without shouting. It is warm without being aggressive, distinctive without being distracting.
Use mochi for: nav accents, active states, links, form focus rings, subtle emphasis text, icon tints, badge outlines, the everyday texture of the interface. Mochi is the colour that earns trust over time.
Dragonfruit #FF006E is the loud sibling. It exists for the moments that need to stop someone mid-scroll: a hero call-to-action, a landing page splash, a campaign banner, a conference booth. It is hot, saturated, and unapologetic. In a field of navy enterprise software it is a deliberate act of contrast.
Use dragonfruit for: hero CTAs, marketing splashes, campaign materials, key conversion buttons, promotional banners, event branding. Dragonfruit is the colour that makes someone remember your name.
Use mochi as the default accent throughout the UI
Reserve dragonfruit for hero moments and conversion points
Let the botanical palette carry the weight of everyday design
Use matsuri colors sparingly. They hit harder when rare
Use dragonfruit for nav accents, form elements, or body links
Put dragonfruit and mochi next to each other. Pick one per context
Make dragonfruit the background of large surfaces
Use matsuri colors for status or semantic meaning. That's what the core palette is for