Command Center

Every change waits for a person who knows

No token reaches your product until someone looks at it. The Command Center shows each change, how it looks in every mode, and who needs to say yes.

Start freeRead the Quickstart
A release waiting for review in the Command Center: a breaking change that needs an Admin, with its token changes and visual check results.

The flow

Four steps, every time

  1. Step 1

    Propose

    Someone edits tokens in the app, from Claude Code or through the API, and bundles the change into a release.

    Shows as draft

  2. Step 2

    Review

    It lands in the Command Center with what changed, what it deprecates and how it looks in every mode.

    Shows as waiting for review

  3. Step 3

    Approve or reject

    A Reviewer or Admin decides. A rejection goes back with a reason, and nothing ships.

    Shows as rejected

  4. Step 4

    Live

    The approved release becomes the one your code exports. The previous one is kept, replaced but not lost.

    Shows as live

Visual checks

See it in every mode before you approve

Each release is checked against your components in each of the theme's modes. Reviewers see at a glance what changed and what stayed the same, instead of reading hex codes.

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.

Rules

Rules that protect you

Breaking changes need an Admin

Removing or renaming tokens can break code. Releases like that wait for an Admin, while Reviewers handle routine changes.

Exceptions are time-boxed

An Admin can let a release skip review in a pinch, but it must expire, and anything longer than a week needs a written migration plan.

A second pair of eyes

A workspace can require that the person who approves is not the person who proposed. Ask us to switch it on.

People and agents

Agents propose. People approve.

Claude Code and the REST API can draft and submit changes, and they go through the same review as everyone else. Approving happens only in the app, by a person with the right role.

Connect Claude Code

Stay in the loop

Nobody has to keep checking

Reviewers get an email and an inbox item when something needs them. Your pipeline gets a signed webhook, so it can rebuild the moment a release goes live.

Webhooks in the docs

  • release.pending_approvalSent when a release is submitted for review.
  • release.publishedSent when a release is approved and goes live.
  • release.rejectedSent when a reviewer rejects a release.

Put review between your tokens and your product

Free for one person. Reviewers and viewers are always free.

Start freeSee pricing