Fragments Cloud is Coming
By Conan McNichollWe've been focused on one thing for the past few months: making Fragments the best component toolkit for AI-assisted development. The CLI, standalone MCP server, contract format, and 66-component UI library are all shipping.
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:
-
Drift detection — Continuous monitoring of connected repositories 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.
-
Design system compliance — Define policies for token usage, accessibility standards, safe props, allowed components, and canonical usage patterns. Cloud checks governed pull requests against them. Think of it as a design system linter that understands AI output patterns.
-
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 is being built around:
- Policy engine — Define rules in code, including
tokens/allowed-prefixes,tokens/require-design-tokens,a11y/standard, safety rules, and component governance rules. Policies run against every governed PR. - Contract verification — Your
.contract.jsonfiles 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 reporting that surfaces governance findings inline once a repository is connected.
- Team analytics — Dashboard showing component usage, violation trends, and compliance scores over time.
- Team workflows — Shared views for design system owners, developers, and AI-agent setup so the same governance model can guide review and generation.
Pricing
We're still finalizing pricing. The UI library remains free and MIT-licensed. The CLI, MCP server, context, and compiler tooling remain publicly available under their current source-available license.
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 opening private beta access gradually. Waitlist members get priority access.
In the meantime, the best way to prepare:
- Add contracts to your components — Run
fragments init --scan src/componentsto generate.contract.jsonfiles for your existing components - Set up the MCP server — Give your AI tools structured access to your design system with
npx -y @fragments-sdk/mcp - Define your theme seeds — Configure your brand, neutral, density, radius, and semantic token inputs so Cloud has a baseline to check against
The public 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.
