Design token governance
Every token change, reviewed before it ships.
Stoaken shows exactly what a change touches, in every mode, and puts a person in charge of approving it. Your AI agents are welcome too. They just don’t get to skip the review.
Free for everyone during early access.
Try it
See what one change touches
This is the Token Graph from inside Stoaken, running on a sample Brand. Pick a change and watch the blast radius.
Token Graph
Acme Design System
44 tokens in view · blast radius: 5 changed
You edited 1 token. 4 more tokens change because they reference it. Nothing is removed, so any reviewer can approve.
Click a group to look inside it. Highlighted parts of the tree are touched by the change; everything else fades back.
The workflow
How a change ships
A person or an agent can start a change. Only a person can finish one.
- Release status: draft
Bring your tokens
Token sets in the W3C design tokens format. Stoaken resolves aliases, brand inheritance and every mode (light, dark, compact, whatever you define) for you.
- Release status: pending_approval
Propose a release
Every combination of modes is resolved and compared with what is live. You see what changed, what it touches, and screenshots of your components in each mode.
- Release status: published
A person approves
Reviewers see the diff, the visual checks and the conversation in one place. Breaking changes need an Admin. Nothing publishes until someone says yes.
Visual checks
Every mode, checked
A change that only affects dark mode should only show up in dark mode. When you submit a release, Stoaken screenshots each component in every combination of modes and compares it with the last published release.
Identical stays quiet. Anything that moved by even one pixel is flagged for a person, with before and after side by side. There is no tolerance setting to hide a real change.
Command Center
One place to decide
The Command Center gathers what is waiting on you across every Brand: releases to approve, with what they deprecate and how their visual checks went, plus comments, delegations and share requests.
Roles do the routing. Reviewers approve routine changes, Admins approve breaking ones, and Viewers can follow along without being able to change anything.
And the rest
Built for how review really goes
Review that fits the team
Comment on a token or a whole release, watch the threads you care about, and hand a review to a colleague when you are away.
Clients can review too
Share a Brand with people outside your organization. They confirm their email with a code and can read or comment, no account needed.
Exceptions, honestly
When a fix cannot wait, an Admin can publish without review. It needs a reason and an expiry date, and anything longer than a week needs a migration plan.
Deprecate in the open
Mark a token deprecated with its replacement. Stoaken lists everything that still uses it, so the migration has a to-do list.
For AI agents
Agents welcome, through the same door
Connect Claude or any MCP client. Agents can read resolved tokens, check what is deprecated and propose changes. A proposal becomes a release waiting for review, exactly like yours.
Agents have no approve or publish action, in the API or the agent tools. Approving is something only a person can do, in the Command Center.
- readlist_brands
- readget_theme_tokens
- readget_resolved_theme_tokens
- readlist_deprecated_tokens
- readlist_releases
- proposepropose_token_change
- proposepropose_token_deprecation
# no approve or publish tool, by design
Pricing
Free for one person. $24.99 per editor for teams.
Reviewers and viewers are always free, so nobody hesitates to bring in the people who should approve. During early access, everything is free.