12 November 2026
Enterprise Design Systems: 8 Real Examples That Scale
An enterprise design system is a design system plus an operating model: versioned releases, a token architecture, governance rules about who changes what, and documentation that multiple teams can build from without talking to each other. The eight systems below are the real thing, verified against their own sites and repositories this week. What separates them from a Figma UI kit is not component count. It is that every one of them survives the moment the people who built it stop being in the room.
The interesting shift in 2026: the most enterprise-grade systems on this list are now documenting themselves for machines. IBM ships an MCP server for Carbon. SAP and Workday keep AGENTS.md files in their component repos. That is the same bet duply makes with DESIGN.md: a design system only scales if the next consumer, human or agent, can read the rules without a meeting.
Why enterprise design systems matter
- Consistency stops being a memory exercise. Figma's guide to enterprise design systems opens with the whole problem in two sentences: "One team can keep a design system in their heads. Five teams, each shipping their own product, can't."
- Tokens carry decisions across teams. The same guide: "Tokens keep the system coherent when nobody has full visibility into it."
- Governance beats tooling. Magic Patterns' July 2026 analysis of enterprise design systems is blunt: "Enterprise design systems are a solved problem technically." They fail on organization, and "over-engineering and under-documenting are the two dominant reasons for design system failure."
- Adoption is the real test. Figma again: "Every time a designer rebuilds a component locally, it signals that the system didn't have what they needed."
- Agents are now consumers. Supernova's 2026 trends report puts it directly: "While previous years were about AI assisting designers, 2026 is about AI agents orchestrating the design-to-code pipeline." Documentation, in their words, "must be a machine-readable intelligence hub."
Here are eight systems that pass those tests, and what each one is best at.
1. IBM Carbon
Carbon describes itself as "IBM's enterprise-ready, open-source design system, shaped by the IBM Design Language."
What it does:
- Open-source component library (42 components in the current docs), currently on v11 with v12 development in public
- Themeable design tokens across four core themes, with React and Web Components as the first-class implementations
- Carbon for AI, "a distinct visual and behavioral identity for AI experiences in IBM products," with AI variants for 12 core components and a dedicated token suite
- Carbon MCP, advertised on the homepage: "Connect AI applications directly to the design system with real-time access to components, tokens, icons, guidance, and code"
- Accessibility as a stated design constraint: "designed and built to be accessible to all, regardless of ability or situation"
Best for: teams building data-dense enterprise software who want the most battle-tested open system available.
Why it makes the list: scale and governance. IBM says Carbon "underpins every digital interaction people have throughout their relationship with IBM," and it is "funded and developed by IBM to meet the company's business needs" while staying open source. It is also the first system on this list to ship its own MCP server, which makes it the reference case for agent-readable design systems.
Tip: Carbon's docs are excellent for humans but spread across hundreds of pages. If you want an agent to apply Carbon-style discipline to your own product, the working pattern is one compact rules file, which is exactly what a DESIGN.md is.
2. Salesforce Lightning Design System 2 (SLDS 2)
Lightning Design System 2 is the current generation of Salesforce's design system, the one every Lightning app and every AppExchange partner builds against.
What it does:
- Components and guidelines for the Salesforce platform: Lightning web components, Aura components, and React applications
- A styling-hooks architecture (CSS custom properties) that replaced hard-coded styles, which is what makes org-level theming possible
- An official SLDS Linter, an npm package that "analyzes your code against Salesforce Lightning Design System 2 (SLDS 2) rules" and "can also apply the suggestions in bulk across your repository and automatically fix your code"
- BSD 3-Clause licensed source for the original system, with axe accessibility tests in the repo
Best for: anyone shipping on the Salesforce platform, which is the point: it is less a choice than a contract.
Why it makes the list: SLDS 2 is the clearest example of design-system-as-enforcement. Salesforce did not just publish guidelines, it shipped a linter that rewrites your code toward them. That is governance expressed as tooling, and it is where every enterprise system is heading.
Tip: the linter model generalizes. An agent with a rules file can do for your codebase what slds-linter does for Salesforce orgs; see give your AI agent a design system.
3. SAP Fiori and UI5 Web Components
SAP consolidated its design guidance under the SAP Design System, and ships the implementation as UI5 Web Components, "an open-source UI components library for building enterprise-ready apps!"
What it does:
- Roughly 85 documented components across the Main and Fiori packages, currently v2.28.1, Apache-2.0 licensed
- Framework agnostic by construction: Web Components that work "with all popular frameworks, including Angular, React," Vue, Svelte and OpenUI5/SAPUI5, with the core framework at about 20 KB gzipped
- Eight built-in themes including high-contrast variants, plus RTL and density modes, which is what multi-region enterprise deployment actually requires
- A dedicated AI package (AI Button, AI Input, AI PromptInput, AI TextArea) plus documented AI interaction patterns
AGENTS.mdandCLAUDE.mdfiles in the repository root, so coding agents get first-party instructions
Best for: enterprise software that must run inside heterogeneous stacks for a decade or more.
Why it makes the list: SAP's system is built for the hardest enterprise constraint, longevity across frameworks. Betting on Web Components instead of any one framework is a governance decision disguised as a technical one. And the repo-level agent files are first-party confirmation that SAP now treats AI agents as a developer audience.
4. Microsoft Fluent 2
Fluent 2 is Microsoft's cross-platform design system, with component sets for web (React), iOS, Android, and Windows.
What it does:
- One design language expressed natively on four platforms rather than one web library ported everywhere
- A two-layer token architecture: "global tokens are context-agnostic and store raw values, like hex codes for color," while "alias tokens are Fluent's second token layer and add semantic meaning to the stored values"
- Tokens that "support OS theming for light, dark, high-contrast, and branded elements, as well as ensure sufficient color contrast"
- Powers Microsoft's own flagship products; the site highlights Teams ("Teams leverages Fluent 2 to boost performance and reduce complexity"), Outlook, and Windows
- First-party accessibility plugins for Figma (focus order, color contrast)
Best for: organizations shipping the same product surface across OS boundaries.
Why it makes the list: the global-to-alias token layering is the textbook pattern for separating raw values from intent, and Fluent documents it more plainly than almost anyone. If you want to understand why semantic tokens matter before adopting them, read Fluent's design tokens page, then see what design tokens are in practice.
5. Atlassian Design System
The Atlassian Design System is the shared language behind Jira, Confluence, Trello, Loom and the rest of the Atlassian suite: "Across all collections, every app feels cohesive and familiar, empowering teams through one design language."
What it does:
- Full foundations layer with published semantic tokens, visible right on the homepage:
color.text.accent.red,elevation.surface.overlay,color.border.brand - Serves three distinct audiences by design: "used internally by Atlassians, Marketplace partners, and other external users"
- Explicit quality bar: "clear standards for accessibility, responsiveness, and enterprise scale"
- Rovo UI, a dedicated AI pattern library for designing agent and chat experiences
- Protobox, Atlassian's in-house AI prototyping app that "turns ideas into interactive, coded prototypes and production-ready specs" built on the system
Best for: multi-product companies where internal teams and third-party developers must ship to the same standard.
Why it makes the list: Atlassian treats its design system as a platform with external customers (Marketplace partners), which forces the documentation discipline most internal systems never develop. Protobox is also the clearest public example of an enterprise pointing AI tooling at its own design system rather than at generic output.
6. Workday Canvas
Workday Canvas is Workday's design system; the implementation lives in the open at canvas-kit, "development kits to implement UI following the Workday Sana Canvas Design System."
What it does:
- Apache-2.0 licensed React component kit, developed fully in public: "All work on the Canvas Kit happens directly on GitHub"
- A standalone token package,
@workday/canvas-tokens-web, with explicit base, brand, component, and system layers delivered as CSS variables - Versioning discipline most systems only claim: "Canvas Kit follows semantic versioning and is enforced automatically by conventional commits," with upgrade guides running from v4 through v16
- A stated support window: "At any given time, we support three major versions of Canvas Kit: previous, current, and next"
- An
AGENTS.mdfile and skills directory in the repo root for coding agents
Best for: teams who care about upgrade paths, deprecation policy, and the unglamorous mechanics of running a system for years.
Why it makes the list: sixteen major versions with documented migrations is the strongest public evidence of design system governance you can get. Most systems show you their components; Canvas shows you its operating model.
7. Porsche Design System
The Porsche Design System is "your all-in-one toolkit for creating high-quality, visually stunning web applications," and the best public example of a brand-first enterprise system.
What it does:
- 58 versioned components (current release v4.10.1) "powered by Web Components with TypeScript and SSR support," with "first-class support for React, Angular, Vue, and Vanilla JS"
- Nine token categories covering blur, border, breakpoint, color, font, gradient, motion, shadow, and spacing
- Public Figma libraries, an icon library, and a brand guide shipped as one package
- A stated principle duply agrees with completely: "The coded components serve as the single source of truth for both design and development"
- Porsche's own benefits page claims the system "enables better collaboration and delivers up to 31% faster implementation"
Best for: brand-led organizations where the design system must encode identity, not just efficiency.
Why it makes the list: most brand design systems are PDF guidelines; Porsche shipped theirs as versioned npm packages. When the brand is the product, putting the brand into code with semver is the whole game.
8. Infor Design System (SoHo)
The Infor Design System is built around SoHo, "Infor's design language, built to capture industry requirements and business role specificity."
What it does:
- Web components and patterns for Infor's industry-specific ERP suites
- Published as
ids-enterpriseon npm, currently v4.111.2, Apache-2.0 licensed - Foundations, components, patterns, and UX writing guidance in one portal
- Designed explicitly around business roles rather than generic UI needs
Best for: ERP and vertical software where users live in the product all day.
Why it makes the list: v4.111.2 is not a typo. Over a hundred minor releases on one major version is what maintenance looks like when thousands of enterprise screens depend on you not breaking them. Infor is the quiet counterexample to redesign-driven systems.
What actually separates enterprise from a component library
Strip the logos away and the eight systems above share four properties:
- Layered tokens. Raw values, semantic aliases, component tokens. Fluent documents the layers, Workday ships them as separate CSS variable files, Atlassian publishes the semantic names. The Design Tokens Community Group's first stable specification (2025.10, per Magic Patterns) now gives this structure a vendor-neutral format.
- Governance you can point at. Who may change a token, how a component gets deprecated, how many majors are supported. Magic Patterns calls the governance model "the most consequential long-term decision," and Canvas's three-version support window is what that looks like written down.
- Enforcement, not aspiration. Salesforce ships a linter. In Magic Patterns' 2026 framing, "AI has shifted from documentation to enforcement," with agents that lint designs and code against system tokens.
- Machine-readable documentation. Carbon has an MCP server, SAP and Workday ship
AGENTS.md, Supernova's trend line says documentation "must be a machine-readable intelligence hub." The enterprise design system of 2026 assumes a non-human reader.
A brand design system, the variant people also search for, is the same structure with a different center of gravity: identity first, efficiency second. Porsche is the shipped example above; Figma's examples roundup points to Uber's Base as "a strong model for scaling design across a global, multi-product ecosystem." The mechanics do not change. The brand just becomes a token layer you refuse to let anyone override.
How to get the same discipline without an enterprise team
You do not need IBM's budget to get the property that makes these systems work, which is rules a new consumer can apply without asking anyone. That consumer is increasingly an AI agent, and the compact format for it already exists:
- Pick a system whose discipline fits your product. Browse the duply library: 550+ products documented as structured design specs, from Linear to Stripe to Vercel.
- Take the DESIGN.md. One file with the tokens and the usage rules, the part of an enterprise system an agent can actually consume. This is the same shape Anthropic uses for Claude's design systems and UX Pilot now centers its generator on.
- Drop it into your repo next to your agent's instructions, and reference it from
CLAUDE.mdorAGENTS.md, exactly as SAP and Workday do in their own repos. - Let the agent enforce it. Every new screen inherits the system; drift becomes a diff you can see. The full setup is in give your AI agent a design system.
FAQ
What is an enterprise design system?
An enterprise design system is a design system built to operate across many teams and products at once. Beyond components and styles, it includes a layered token architecture, versioned releases, governance rules for contribution and deprecation, accessibility standards, and documentation complete enough that teams can build from it independently. IBM Carbon, Salesforce Lightning Design System 2, and SAP Fiori are canonical examples.
What is the difference between an enterprise design system and a UI kit?
A UI kit is a set of reusable visual components. An enterprise design system adds the operating model: design tokens that separate raw values from intent, semantic versioning with migration guides, governance over who changes what, and enforcement tooling such as linters. A UI kit tells you what a button looks like; an enterprise system guarantees ten teams ship the same button next year.
Which companies have the best enterprise design systems?
The strongest public examples are IBM (Carbon), Salesforce (Lightning Design System 2), SAP (Fiori with UI5 Web Components), Microsoft (Fluent 2), Atlassian, Workday (Canvas), Porsche, and Infor (SoHo). Each publishes its system publicly, versions its releases, and documents governance rather than just components.
What is a brand design system?
A brand design system is an enterprise design system whose primary job is encoding brand identity rather than UI efficiency: logo rules, color, typography, motion, and voice expressed as reusable, versioned assets. The Porsche Design System is the clearest shipped example, delivering brand-faithful components as npm packages rather than PDF guidelines.
Are enterprise design systems open source?
Several are. IBM Carbon, SAP UI5 Web Components, Workday Canvas Kit, and Infor's ids-enterprise are Apache-2.0 licensed; the original Salesforce Lightning Design System source is BSD 3-Clause. The license covers the code, not the identity: you can build on Carbon's components, but shipping something that looks like IBM is a different question. See our guide to open source design systems.
What are design tokens in an enterprise design system?
Design tokens are named values that store design decisions, such as colors, spacing, and typography, so they can be referenced instead of hard-coded. Enterprise systems layer them: global tokens hold raw values, alias or semantic tokens add meaning like action.primary, and component tokens bind them to specific elements. The Design Tokens Community Group published its first stable specification for the format in October 2025.
Can AI agents use enterprise design systems?
Increasingly, yes, and the vendors are building for it. IBM advertises Carbon MCP for connecting AI applications directly to components, tokens, and guidance. SAP's UI5 Web Components and Workday's Canvas Kit both keep AGENTS.md instructions in their repositories. For your own product, the equivalent is a DESIGN.md file: tokens plus usage rules in one document an agent reads before generating UI.
How long does it take to build an enterprise design system?
The public evidence says years, not months. Workday Canvas has shipped sixteen major versions; Infor's ids-enterprise is past its hundredth release on v4. The practical shortcut is not building faster but starting from the part that creates consistency, the documented rules, and growing components behind them. That rules-first path is what a DESIGN.md workflow gives you on day one.
The eight, ranked
- IBM Carbon: the most complete open enterprise system, and the first with its own MCP server.
- Salesforce SLDS 2: governance as tooling; the linter that fixes your code is the future of enforcement.
- SAP Fiori / UI5: framework-agnostic longevity, with AI components and agent instructions shipped first-party.
- Microsoft Fluent 2: the cleanest public explanation of layered tokens across four platforms.
- Atlassian: platform-grade docs serving internal teams and Marketplace partners alike.
- Workday Canvas: versioning and upgrade discipline nobody else matches in public.
- Porsche: the brand design system benchmark, shipped as code with semver.
- Infor SoHo: industry-role specificity and hundred-release maintenance.
The fastest way to borrow their discipline: open the duply library, pick the system that matches your product's ambition, and give your agent the DESIGN.md. The enterprise part was never the component count. It was the rules surviving handoff, and that is now a one-file problem.