Tokene
Sign inGet started
Design tokens, governed

Tokene is a spec-driven platform for design tokens — drafts, change requests, immutable releases, and deterministic exports your build can trust.

Get startedSign inv2026.05.15
tokens / color.brand.500draft
Name
color.brand.500
Value
#2f6feb
Type
color
Group
brand
Refs
—
Release
—
Referenced by 14 tokenslive
02The product loop

Every token change flows through the same governed path.

Published tokens are never edited directly. A draft becomes a change request, gets reviewed, lands in a release, and is exported as an immutable snapshot.

  1. 01
    Draft
    Author proposes a token or edit.
  2. 02
    Change Request
    Bundle changes for review.
  3. 03
    Review
    Approvers validate intent and impact.
  4. 04
    Release
    Immutable snapshot is taken.
  5. 05
    Export
    Deterministic artifacts ship downstream.
03What you get

Built for teams that ship tokens to production.

A small set of opinions, applied consistently: validate early, snapshot on publish, export deterministically, audit everything.

Validated references
{color.brand} resolves recursively. Cycles are caught. Type-aware checks on every save, approval, and import.
Immutable snapshots
Exports read from the snapshot the release was published with — never live state. Builds stay reproducible.
Draft-first changes
Drafts flow draft → in-review → approved → published. Live values stay visible until the release lands.
Workspace isolation
Every entity is workspace-scoped and gated by Postgres RLS. RBAC enforced at the database boundary.
Deterministic exports
CSS, SCSS, TypeScript, Style Dictionary. Sorted by name, stable formatting, version stamped.
Signed webhooks
HMAC-SHA256 signed deliveries and an email relay. Every external endpoint is in your control.
04Exports

One source. Every format your build expects.

Each exporter is deterministic — tokens sorted by name, stable formatting, exporter version stamped.

  • Reads from immutable release snapshots
  • Reproducible diffs across releases
  • Available via REST API or downloadable artifact
  • Webhook-driven CI integration
tokens.css
:root {  --color-brand-500: #2f6feb;  --color-brand-600: #1e54c6;  --color-bg-surface: #ffffff;  --color-text-default: #0b0d10;  --space-2: 8px;  --space-3: 12px;  --radius-md: 8px;}
exporter v3.4.0 · sorted by namedeterministic
05Governance

Auditability across every critical action.

Every mutating action writes an audit row. Notifications fan out in-app and to your endpoints. Reviews capture intent and rationale, not just diffs.

Breaking-change detection
Edits flagged when values shift in ways that affect consumers.
HMAC-signed webhooks
Every external delivery includes x-tokene-signature.
Row-level security
Workspace isolation at the Postgres boundary.
Approval gates
Stale CRs disabled automatically after a publish.
06Frequently asked

The short answers.

How is this different from a token JSON file in Git?
Tokens get validated, referenced, reviewed, and snapshotted as a unit. The same governance you expect from code review, plus deterministic exports your build trusts.
What formats does it export?
CSS custom properties, SCSS variables, a typed TypeScript module, and Style Dictionary–compatible JSON. Each export is sorted and version-stamped so diffs stay clean.
Can multiple teams share one instance?
Yes. Every table is workspace-scoped with Postgres row-level security. Members are invited per workspace with roles enforced at the database boundary.
What happens when I publish?
A workspace-scoped mutex is acquired, published tokens are snapshotted, the reference graph is refreshed, and open change requests are re-validated against the new state.
07Start

Bring rigor to your design tokens.

Create a workspace, invite your team, and run your first release in minutes.

Create workspaceSign in