The design system workspace

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

Stoaken is where design system teams shape tokens visually, trace what a change touches, compare any two versions and approve every release. AI agents can propose changes too. They just don’t get to skip the review.

Start freeTry it below

Free for everyone during early access.

Edit tokens by looking at them

  • Drag a ramp’s lightness curve, nudge spacing and radius in place, or switch to the Table for bulk moves, renames and deprecations.
  • Switch the mode and every value shows as it is in Dark, Compact or any mode you define. Edits in a mode go to that mode’s own set.
  • Text pairs show their contrast; put any two modes side by side and drag the divider.
Tokens · Acme · Core Live demo · nothing is saved

Specimen shows a token set the way designers think about it: ramps, type, spacing and contrast, editable in place, in every mode.

Open this page on a computer to try it live.

Modes

Every mode, edited and checked

  • Edit a mode where you see it. Switch to Dark and change a value: it goes into Dark’s own set and nowhere else. A mode without one gets it in a click.
  • Compare any two. Put Dark Compact beside Light Comfortable, or any pair, with contrast ratios on both sides.
  • Screenshot every combination. Each release captures your components in every mode and compares them with the last one. Identical stays quiet; anything that moved by a pixel is flagged for a person, before and after side by side.
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 (v3), an @theme block (v4, CSS or SCSS) or W3C design tokens JSON. Stoaken reads Tailwind configs without running them and keeps only what you changed from Tailwind’s defaults. Try it:

The workflow

How a change ships

A person or an agent can start a change. Only a person can finish one.

  1. Shape it

    Edit in Specimen or the Table, import from Tailwind, or let an agent propose. Every mode resolves as you work, and each save is kept so you can go back.

  2. Propose a release

    Every mode is resolved and compared with what is live. Reviewers see what changed, what it reaches, and screenshots of your components in each mode.

  3. A person approves

    Breaking changes need an Admin, and a workspace can require someone other than the author. Nothing publishes until a person says yes.

Built for teams

Review that fits how teams really work

The Command Center gathers what is waiting on you across every Brand. Around it, everything a team needs to change a design system without surprises. How review works

  • Roles that route

    Reviewers approve routine changes, Admins approve breaking ones, Viewers follow along. Reviewers and viewers are free.

  • Approve in batches

    Clear a queue in one go. Each release still gets its own checks, and the ones you can’t approve say why.

  • History and restore

    Every save of a token set is kept. See what changed since any of them and bring one back as unsaved edits.

  • Compare anything

    Two releases, or a release and your work in progress, in any mode, with renames and deprecations called out.

  • A record of every decision

    Activity shows who invited, approved, published or changed access, and when. Export it as a spreadsheet.

  • Clients review too

    Share a Brand with people outside your company. They confirm their email with a code and can read or comment, no account needed.

  • Deprecate in the open

    Mark a token deprecated with its replacement and see everything that still uses it, so the migration has a to-do list.

  • Brands that inherit

    A product Brand can build on a parent. Change the parent once, and every child sees exactly what it inherits.

For developers and AI agents

Agents welcome, through the same door

Connect Claude or any MCP client. Agents read resolved tokens, check what is deprecated and propose changes. A proposal becomes a release waiting for review, exactly like yours. The same is true of the REST API and the CLI.

Agents have no approve or publish action, in the API or the agent tools. Approving is something only a person can do.

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
  • readlist_brands
  • readget_theme_tokens
  • readget_resolved_theme_tokens
  • readlist_deprecated_tokens
  • readlist_releases
  • 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
  • proposepropose_token_change
  • proposepropose_token_edits
  • proposepropose_token_deprecation

# no approve or publish tool, by design

Trust

Built so the right person decides

Your design system is product infrastructure. Stoaken treats it that way, from the database up. We reviewed the whole codebase for security in October 2026 and fixed what we found.

  • People approve

    There is no approve or publish action for agents or API keys. A release only goes live when a person says yes.

  • Access in the database

    Every read and write is checked by row-level security in Postgres, so the database itself refuses what you can’t see.

  • Signed, guarded integrations

    Webhooks are signed (Standard Webhooks). Outbound calls refuse private networks and don’t follow redirects.

  • Locked-down sessions

    Sealed, http-only cookies, sign-in protected against forged links, and pages that can’t be framed by other sites.

  • Sandboxed components

    Your component code runs in an isolated frame with its own content policy, never with access to your session.

  • Exceptions leave a trail

    Publishing without review takes an Admin, a reason and an expiry date, and it shows up in the Command Center until it’s resolved.

Made for long days

A desktop tool, not a dashboard

Keyboard first, views that remember how you left them, and instruments that stay quick on design systems with thousands of tokens.

  • KSearch a whole Brand: tokens by name or colour, components, releases, comments
  • MNext mode
  • \Swap the compared sides
  • [Previous column or group
  • ?Every shortcut on the page

Who it’s for

Built for the people around a design system

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.

Start freeSee pricing