The design system that powers
every Dana venture.
Nodus Design System is the shared component and token layer behind Iris, FullFare, Nodus, and every future Dana venture. 79 components. Semantic token system with multi-brand theming. WCAG 2.1 AA+ throughout. When a new product ships, the design language is already there.
One design language. Every product inherits it.
Design systems that live in a separate repo and a separate process get out of sync. The Nodus Design System doesn't sit beside the products — it runs underneath them. Every component Dana ships across Nodus, Iris, and FullFare draws from the same token layer and the same 79-component library.
A coherent design language isn't a style guide decision. It is an organizational infrastructure decision. We made it once.
Multi-brand theming means each venture expresses its own identity through token overrides — not forks, not custom components. Dana's token architecture keeps brand expression and structural consistency orthogonal to each other.
Built to last, not built to ship once
Theming without component forks
Swap @nodus/tokens for brand-specific values without touching a single component. Design intent lives in the token layer — not hardcoded into markup.
WCAG 2.1 AA+ throughout
Focus management, ARIA semantics, and contrast ratios — built in from the start. Accessibility isn't a compliance checkbox retrofitted at the end. Every component ships accessible by default.
Web, mobile, dark mode, RTL
79 components available across web and mobile (Expo/React Native). Dark mode and RTL support throughout. When Dana ships to a new surface, the component set is already there.
Components for agent-driven UIs
Designed for interfaces where state changes fast and context surfaces programmatically. Status indicators, audit trails, and structured data displays — the primitives that AI-native products need from day one.
Seven principles. Every component follows all of them.
The A2UI protocol defines how AI-native interfaces should behave. These aren't guidelines — they're constraints. Every Nodus component is designed to be implementable without violating any of them.
Visibility Over Invisibility
Make the algorithm present, not hidden. Default to revealing what's happening. The starting assumption is revelation — not the other way around.
Ceremony Over Efficiency
Important actions should feel weighty. Granting an AI access to your calendar isn't a checkbox — it's a decision with consequences. Friction, applied deliberately, creates meaning.
Auditability as Aesthetic
The ability to trace what happened — who acted, when, why, with what outcome — is a design value, not a compliance requirement. Beautiful systems are inspectable systems.
Temporal Honesty
Represent time accurately. If data is two hours old, say so. Don't collapse time into a false 'now'. Staleness, latency, and duration are first-class interface properties.
The portfolio has a shared nervous system. Design is part of it.
Dana's thesis is that organizational design is a primary competitive moat. That means context compounds, decisions are logged, and nothing is rebuilt from scratch unnecessarily. The design system is a direct expression of that principle.
When Iris ships a dashboard or FullFare ships a driver interface, they are not starting from blank. They inherit a design language already tested in production across Nodus. Every new surface benefits from every surface that came before.
Explore the system
Documentation, token reference, component specs, and the full A2UI principle explorer are available at design.dana.xyz.