March 15, 2026·fragments cloud

Fragments Cloud is Coming

By Conan McNicholl

We've been focused on one thing for the past few months: making Fragments the best open-source component toolkit for AI-assisted development. The CLI, MCP server, contracts system, and 67-component UI library are all shipping and stable.

Now we're building the next layer: Fragments Cloud.


What is Fragments Cloud?

Fragments Cloud is a hosted governance platform for teams shipping AI-generated interfaces. It sits between your design system and your AI tools, catching problems before they reach production.

Three capabilities:

  1. Drift detection — Continuous monitoring of AI-generated code against your component contracts. When an agent uses a component incorrectly, violates an accessibility rule, or invents a pattern that doesn't exist in your system, Cloud flags it.

  2. Design system compliance — Define policies (seed enforcement, palette compliance, token usage, accessibility rules) and Cloud checks every AI-generated PR against them. Think of it as a design system linter that understands AI output patterns.

  3. Team dashboards — See which components are being used, which are being misused, and where agents are drifting from your system. Track compliance over time across your whole team.


Why governance matters now

AI coding assistants are getting better at generating UI. That's the problem.

When an agent is bad at UI, teams catch mistakes in review. When an agent is good enough that code looks plausible, violations slip through. A component that's almost right — wrong variant, missing aria label, hardcoded value instead of a token — passes visual inspection but degrades your system over time.

The pattern we've seen across early adopters:

  • Week 1: AI output matches the design system perfectly
  • Week 4: Subtle drift — the AI starts mixing patterns, inventing props, skipping accessibility
  • Week 8: The codebase has two design systems — the real one and the one the AI imagined

Governance isn't about blocking AI. It's about keeping the quality bar that made your design system worth having in the first place.


What's included

Fragments Cloud will launch with:

  • Policy engine — Define rules in code (enforce-seeds, palette-compliance, wcag-aa, aria-labels, focus-order). Policies run against every governed PR.
  • Contract verification — Your .contract.json files become the source of truth. Cloud verifies that AI-generated code respects the props, variants, accessibility rules, and banned patterns you defined.
  • GitHub integration — PR checks that report violations inline. No extra tooling or workflow changes.
  • Team analytics — Dashboard showing component usage, violation trends, and compliance scores over time.
  • Multi-persona support — Different views for designers (visual drift), developers (code violations), and AI agents (contract adherence).

Pricing

We're still finalizing pricing. The open-source toolkit (UI library, CLI, MCP server, compiler) remains free and MIT-licensed — that doesn't change.

Cloud will be a paid product for teams. We'll share pricing details before launch. If you want to be first in line, join the waitlist.


Timeline

We're targeting a private beta in the coming weeks. Waitlist members get priority access.

In the meantime, the best way to prepare:

  1. Add contracts to your components — Run fragments init --scan to generate .contract.json files for your existing components
  2. Set up the MCP server — Give your AI tools structured access to your design system via fragments mcp
  3. Define your seeds — Configure your 5 seed values (brand, neutral, density, radius, danger) so Cloud has a baseline to check against

The open-source toolkit is the foundation. Cloud is the enforcement layer. Together, they give you confidence that AI-generated UI meets your standards — not just today, but as your team and your AI tools evolve.

We'll share more as we get closer to launch. Follow along on GitHub or X.

Conan McNicholl
Conan McNichollFragments