The design system workspace

See every change. Check every mode. Ship it with a yes.

Shape your design system by eye. See what every change touches. Ship only what your people approve. Agents can propose. They never get an approve button.

Free during early access.

How it works

One token change, from the first edit to every product that uses it

Follow a real release through Stoaken: shaped, traced, checked, approved and shipped. Real screens from the app, shown with demo data.

  1. 01 Shape

    Edit tokens by looking at them

    Every palette is a ramp you shape by eye. Drag a step lighter or darker and see where it’s used. Text pairs show their contrast as you go, and each mode is edited in place: a change in Dark stays in Dark.

    Stoaken’s Tokens page: the emerald, plum, night and stone palettes as ramps of swatches, each with a lightness curve and the tokens that use each step.
    1. Drag a dot to set a step’s lightness; under each step, the tokens that use it.
    2. Every palette, light to dark, on one page.
  2. 02 Trace

    See everything a change will reach

    Tokenwright draws your system as one flow, from raw values to the components that use them. Pick a token and its family lights up, so you know what a change touches before you make it.

    Tokenwright’s Flow with color.brand.primary selected: its lines light up, and the inspector says 2 tokens and 2 components change if it does, with its lineage back to palette.emerald.700.
    1. The token you picked, and the lines to everything that points at it.
    2. Reaches: 2 tokens and 2 components change if this does.
    3. Its lineage, back to the raw value.
  3. 03 Check

    Look at the change before anyone says yes

    Every release is drawn on your real components twice, before and after, with the proposed tokens. Stoaken counts what looks different, so reviewers spend their attention where it matters. Component code runs in a sealed sandbox on a domain of its own.

    Reviewing v1.3.0: visual checks say 2 of 30 look different, with 28 alike; the approvals timeline; and the Showcase with Before | after, Side by side and Try it.

    Try it: the Button, drawn before and after v1.3.0

    1. 2 of 30 components look different. The other 28 need no second look.
    2. Before and after on the components the proposer picked.
  4. 04 Decide

    People approve. Agents propose.

    Approve it, send it back, or hand it to a colleague. Your rules decide who has to say yes, and breaking changes need an Admin. Agents and API keys can propose changes, but they have no approve or publish action.

    The decision panel for v1.3.0: You’re asked, asked of 1 person; 6 components use what changes; Approve, Send back and Hand off.
    1. Approve: only a person can.
    2. Who’s asked, and how far the votes have come.
    3. Away? Hand it off.
  5. 05 Ship

    Send it everywhere your system lives

    One release, every destination: Figma and Penpot for design; CSS variables, Tailwind, TypeScript, Swift and Jetpack Compose for code; the CLI, the API and MCP for pipelines and assistants. 12 export formats from one source of truth.

    The rollout for v1.3.0: Where does it need to go? Penpot and Figma for design tools; CLI, CSS variables, Tailwind, TypeScript, iOS, Android and API / CI for the codebase; an AI assistant and webhooks.
    1. Figma: the Stoaken plugin updates Figma’s variables to this release.
    2. Code: custom properties for any web stack, every mode included.
    3. Assistants read the tokens over MCP; webhooks tell your systems.
  6. 06 Live

    Know when it’s live, everywhere

    Each release path is signed off by its owner, or lands on its own when your CI check passes. Once every required path has landed, a release lead flips it live and everyone on the Brand sees it. In Figma, the designer brings the same release in, one mode per Stoaken mode.

    The rollout for v1.2.0: release paths, 1 of 2 landed (Web app landed via CI, iOS app waiting), and Go live.
    Stoaken for Figma, signed in as Maya Lindqvist on Stoaken Web: v1.2.0 is live in Stoaken, with Bring v1.2.0 into Figma.
    1. Landed via CI: the check passed.
    2. Go live: one switch, once every required path has landed.
    3. In Figma: the same release, ready to bring in.
Stoaken’s Tokens page: the emerald, plum, night and stone palettes as ramps of swatches, each with a lightness curve and the tokens that use each step.
Tokenwright’s Flow with color.brand.primary selected: its lines light up, and the inspector says 2 tokens and 2 components change if it does, with its lineage back to palette.emerald.700.
Reviewing v1.3.0: visual checks say 2 of 30 look different, with 28 alike; the approvals timeline; and the Showcase with Before | after, Side by side and Try it.

Try it: the Button, drawn before and after v1.3.0

The decision panel for v1.3.0: You’re asked, asked of 1 person; 6 components use what changes; Approve, Send back and Hand off.
The rollout for v1.3.0: Where does it need to go? Penpot and Figma for design tools; CLI, CSS variables, Tailwind, TypeScript, iOS, Android and API / CI for the codebase; an AI assistant and webhooks.
The rollout for v1.2.0: release paths, 1 of 2 landed (Web app landed via CI, iOS app waiting), and Go live.
Stoaken for Figma, signed in as Maya Lindqvist on Stoaken Web: v1.2.0 is live in Stoaken, with Bring v1.2.0 into Figma.

The product

Calm screens for every part of the work

Real screens from Stoaken, shown with demo data: from what needs you this morning to the release you approve.

Stoaken’s Overview: Up next, then cards for Needs you (one release to review), Live now (v1.2.0 with v1.3.0 in review), What changed this week, Health, People and Brands.

What needs you, what’s live and what changed, for every Brand, the moment you sign in.

For designers

A visual playground that ships safely

Build by eye. See it on real components. Ship it reviewed. Stoaken for designers

  • Palette · try a seed

    Palettes and scales

    One colour becomes light and dark ramps, each step’s readability shown.

    Design tools
  • A Brand Book in five layouts

    Rebuilt by every release, arranged the way you like.

    Brand Book
  • Icons & Logos

    Lucide, Material or your own, plus logo sets with a favicon pack.

    Icons & Logos
  • Figma, measured

    Components come in with a score for how close they are to Figma.

    From Figma
    Figma
    Stoaken
    A real result: the Card from our Figma test file. Most of the gap is its photo.

Your real components, in every review

Reviewers see the button, not the hex code. Every component, drawn with your tokens, in every mode.

  • Three ways inA folder, your code or CI, or a Figma selection.
  • Decide before it landsClashes are asked about first. All of it imports, or none of it.
  • A wall that wakes upEvery card shows its latest picture, and runs live when you look.
  • Sealed previewsImported code can’t reach your account, your data or the internet.

Dark mode is never an afterthought

  • Edit the mode you’re looking at. A change in Dark stays in Dark.
  • Compare any two. Side by side, with contrast on both.
  • See every mode it touches. If a pixel moved, a person sees it before it ships.
Visual checks for a release: the order card is unchanged in light mode and changed in dark mode, shown before and after side by side.

Bring your tokens

Start from what you already have

Paste a Tailwind config, an @theme block or W3C tokens JSON. Stoaken keeps only what’s yours. Try it:

Your config

Edit it: Stoaken reads the config as text and never runs it.

Your Brand in Stoaken

Built for teams

Fast, and never a surprise

A person or an agent starts a change. Your people and your rules decide how it ships. See the review desk

New release

Stoaken Web v2.4.0

6 changes · 1 breaking · dark mode only

Goes to

Design leads Sam Lindiwe

Only they’re asked. Their desk says Asked you

How releases work

For developers and AI agents

Agents welcome, through the same door

Connect Claude or any MCP client. Agents read your tokens and propose changes. Every proposal goes through your review rules, the same as a person’s. So do the API and CLI.

No approve button for agents. Saying yes is a person’s job.

Exports to 12 formats

  • CSS variables
  • CSS, light and dark
  • JSON (W3C)
  • JSON (Style Dictionary v4)
  • JavaScript
  • TypeScript
  • SCSS
  • Tailwind config
  • Tailwind 4 theme
  • Swift (SwiftUI)
  • Jetpack Compose
  • Android XML
  • readget_started
  • readlist_brands
  • readget_brand
  • readget_token_set
  • readget_theme_tokens
  • readget_resolved_theme_tokens
  • readlist_deprecated_tokens
  • readlist_releases
  • readsummarize_release
  • readrelease_changes
  • readrelease_timeline
  • readexport_tokens
  • readlist_webhooks
  • proposecreate_webhook
  • proposeupdate_webhook
  • proposerotate_webhook_secret
  • proposeping_webhook
  • readlist_members
  • proposecreate_workspace
  • proposeinvite_members
  • proposerevoke_invitation
  • proposecreate_theme
  • proposeupdate_theme
  • proposedelete_theme
  • proposecreate_token_set
  • proposecreate_theme_axis
  • proposecreate_theme_mode
  • proposeset_mode_binding
  • proposeadd_icons
  • readscan_icon_usage
  • proposeadd_icons_by_name
  • proposeadd_logos
  • proposepropose_asset_release
  • readfind_tailwind_defaults
  • proposepropose_token_change
  • proposepropose_token_edits
  • proposepropose_token_deprecation

# no approve or publish tool, by design

Trust, built from the database up

Your design system is product infrastructure. We treat it that way: the whole codebase was reviewed for security in October 2026, and what we found is fixed.

Free for two editors. From $14.99 per editor for small teams.

Reviewers and viewers are always free, so everyone who should have a say gets one. During early access, everything is free.