# Fenly

> Fenly is a design system manager for small teams. Tokens, components and docs live in one place; Pluto, Fenly's AI agent, drafts changes; a person approves them; and Figma, code and the published docs stay in step. Fenly is in early access: there is a waitlist and no public pricing yet.

## What Fenly does

- Design tokens for every mode and brand (Light, Dark, multiple brands), with the alias chain behind each value. Format: DTCG.
- Components built only from tokens, in React with Tailwind, Vue and Web Components, with a live playground. Raw values block publishing.
- Docs built from live components, published on the team's own subdomain for their team and clients.
- A health score that combines token usage, accessibility, docs and Figma parity, with "Fix with Pluto" on every issue.
- Two-way Figma sync through the Fenly plugin. Fenly is the source of truth: Figma edits come back as change requests, never as silent overwrites.
- GitHub: approved changes open a pull request with every export format.
- An MCP server for each design system, so AI coding tools read the real tokens and components.
- Exports: CSS variables, Tailwind, DTCG JSON, iOS and Android, at any time.

## Pluto, Fenly's AI agent

Pluto builds tokens and components from a short brief, finds issues, drafts fixes and explains his reasoning. He never changes anything on his own: every change is a change request that someone with review rights approves, edits or sends back. The credit cost of an AI action shows before Pluto starts. More, including a one-minute film of Pluto at work: https://fenly.io/pluto

## Who it is for

- Design system teams of 1 to 5 people
- Freelancers and agencies who run design systems for clients
- Startups that don't have a design system yet

## Status and access

- Early access opens in small groups, in the order people join the waitlist.
- Pricing will be shared before early access ends. Viewers and client guests will always be free.
- Each person who joins with someone's invite link moves that person 50 spots up.

## Who builds it

Fenly is built by Felipe Linares, a product designer with 15+ years in SaaS products and design ops, based in Bogotá, Colombia (https://flinbu.co).

## Blog

Practical notes for small design system teams and Fenly's build log, by Felipe Linares (https://fenly.io/blog).

- [What is design system drift, and how do you catch it early?](https://fenly.io/blog/design-system-drift): Design system drift is the slow gap between what your design system says and what actually ships. It starts with small, reasonable shortcuts, like a hard-coded hex or a forked component, that nobody reviews. You catch it early by keeping one source of truth, checking for raw values, and making every change small and reviewed.
- [Why I’m building Fenly, and the one rule it can’t break](https://fenly.io/blog/why-im-building-fenly): Fenly is a design system manager for small teams, and its one rule is that Pluto, its AI agent, proposes and a person approves. Pluto drafts every change as a change request with its steps and checks, the credit cost shows before it starts, and nothing in your design system changes until someone with review rights approves it.

## Links

- [Home and waitlist](https://fenly.io/)
- [FAQ](https://fenly.io/#faq)
- [Meet Pluto, Fenly's AI agent](https://fenly.io/pluto)
- [Film: Pluto at work, one minute](https://www.youtube.com/watch?v=pJfDyUGFYiU)
- [Privacy](https://fenly.io/privacy)
- [Terms of Service](https://fenly.io/terms)
- [Contact](https://fenly.io/contact): hello@fenly.io