Releases
Ship tokens like code, approved by the people who should say yes
A token change is a release: built on one page, sent to the right reviewers, voted on if you like, held to your approval policies, published on time, and announced to your pipelines.
Live demo
A release under review: every change mode by mode, the components it reaches, and the approvals it still needs.
Open this page on a computer to try it live.
From an edit to production
01
A release, built on one page
Pick the theme, see every change mode by mode, get a suggested version, choose reviewers and when it goes live. Or edit tokens and press Save and create release.
- 02
The right reviewers, not everyone
Send it to people, to groups like Design leads, or both. Only they are asked, and the desk tells them “Asked you”.
- 03
Approval policies nothing can skip
Pick who must approve, workspace-wide or per Brand, for every release or only breaking ones. Enforced in the database, so no screen, API call or script can publish around them.
- 04
Votes, live
Open a release, or single tokens in it, to a vote: everyone or chosen groups, with a closing time. The tally moves as people vote. Votes advise; people decide.
- 05
Scheduled, or straight away
Approve now and publish at a set time; the live release stays live until then. Or publish the moment it’s approved.
- 06
Every component it reaches
Each review lists the components a change touches, directly, through aliases or through the components they use, and whether their screenshots changed.
- 07
Your pipeline hears it
Signed webhooks for submitted, published and rejected, with change counts and a breaking flag. A lab to send a real sample, check signatures, and recipes for GitHub, Vercel, Slack and more.
- 08
A history you can trust
Who proposed, who it was handed to, who approved and when, on every release, and in the workspace activity log.
- 09
The whole picture on Overview
Waiting, approved and going live, recently live, open votes, recent edits and integration health, the moment you sign in.