For engineers

Tokens you can trust in your build

Pull the live release into your code in the format you already use. When a release goes live, your pipeline hears about it.

Start freeRead the Quickstart

In your code

One command, the format you need

12 export 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.

  • The CLI

    stoaken export writes the live release to a file you commit, so a build never picks up an unreviewed change.

    CLI docs

  • Light and dark in one file

    CSS that switches with prefers-color-scheme, or per-mode files, generated from the same reviewed release.

    Export formats

Automation

Part of your pipeline, not another tab

  • REST API

    Read tokens, propose changes and manage webhooks with an API key that has exactly your access. OpenAPI included.

    API reference

  • Signed webhooks

    Rebuild the moment a release goes live. Secrets rotate with a day of overlap.

    Webhooks

  • Claude Code and other agents

    Agents can propose token changes through MCP. They go through the same review; only people approve.

    Connect an agent

  • Your components, checked

    Bind component props to tokens and every release screenshots them in every mode, so a reviewer sees the real effect.

    Visual checks

Stop copying hex codes from screenshots

Free for one person. Connect your build in minutes.

Start freeSee pricing