Pluto proposes. A person approves.
Pluto is Fenly’s AI agent. He builds your tokens and components, finds what’s drifting and drafts the fix. Nothing changes until someone on your team approves it.
One minute with Pluto
From a brief to a release: Pluto builds, checks and proposes, and a person approves every change.
What Pluto does today
Everything on this list is built. Each job ends the same way: a change request for a person to review.
Builds your system from a brief
Write a brief in steps, or start from your brandbook or website. See the cost first, then watch Pluto build the plan, your tokens and 12 starter components.
Finds the drift
The health check lists raw values, missing dark values and low contrast. Click Fix with Pluto on any issue and get the fix as a change request.
Keeps contrast in check
Change a brand color and Fenly checks every pair in Light and Dark. When one fails, Pluto proposes the shade that passes.
Builds components with you
Describe a component and Pluto writes it with your tokens, runs the checks and shows a live preview before anyone approves it.
How a change request works
Pluto never edits your system directly. Every job, big or small, arrives as a change request you can read, edit and approve.
Ask, or let Pluto spot it
Ask in the chat, or click Fix with Pluto on a health issue. The credit cost shows before anything runs.
The askPluto drafts the change
You get what changes, why, and the checks Pluto ran. Edit any value or leave a comment.
Pluto’s reply and the proposalA person decides
Someone with review rights approves it into main or sends it back. Every change keeps a name in the history.
Approve or reject
Can you fix the contrast in Dark mode?
I found 4 text colors under 4.5:1 on dark surfaces. I moved them one step lighter and left every other token as it is.
What Pluto never does
These are rules built into Fenly, not settings someone has to remember to turn on.
- NeverMerges into main on its ownOnly someone with review rights can approve a change request.
- NeverEdits outside a change requestEvery token, component and fix waits as a proposal you can read first.
- NeverStarts a job without showing the costYou see the credits a job will use before Pluto begins.
- NeverHides how he got thereEach proposal lists the steps Pluto took and the checks he ran.
Pluto lives in your workspace and you can chat with him, but his work arrives as change requests you review. You don’t copy and paste answers.
No. Every change waits for someone with review rights, who can approve it, edit it or send it back.
Pluto’s work uses credits, and you see the cost before any job starts. Pricing comes before early access ends; viewers and client guests stay free.
The change request says so. If a component doesn’t come out right, it’s listed to build later instead of breaking the rest.
Not yet. Figma sync is on the roadmap; today Pluto works on tokens, components and health checks inside Fenly.
Work with Pluto from day one.
Join the waitlist and we’ll email you once, when your spot opens.