Everyone in one brand. Roles decide who can change it.


Checking your account…
Tokens, guidelines and assets in one workspace. Review, publish, and serve exactly that release to teams, pipelines and agents.


color.accent #FAFAFA → #4E8CFF
Brands don’t break in the brand book. They drift in between: a hex value pasted by hand, a logo saved into the wrong repo, an agent that guesses. Randr replaces the copies with one release everyone reads.
- logo_final_v3_NEW.svg- color: #2f6b54; /* close enough */- "Use the brand green." (agent guesses)+ randr pull ✓ sha256 verified+ var(--color-forest) from release v15+ get_design_tokens → css read-only
| What you need | Brand portal | Design library | Tokens in a repo | Randr |
|---|---|---|---|---|
| Tokens, guidelines and assets together | Assets and docs | Styles and components | Tokens | ✓ All three |
| Immutable releases, compare and restore | — | Library versions | Git tags | ✓ Built in |
| Agent access with scoped credentials | — | Varies | Repository access | ✓ MCP, REST and CLI |
| New releases arrive as pull requests | — | — | Manual | ✓ randr/sync-… branch |
A release moves through four steps. Everyone downstream reads only the last one.










A release pins exactly which tokens, guidelines and assets belong together. Drafts float above it until someone publishes. Select a layer.
limits.tokens_per_import = 2000limits.asset_size = "25 MiB"agent.tools = 13 # 11 read, 2 proposeroles = ["viewer", "editor", "admin", "owner"]Everyone in one brand. Roles decide who can change it.


Compare any two releases. Restore an old one as a new release.


Agents call MCP tools. Changes arrive as proposals, never as releases.


A lockfile for your brand. Pinned in CI, updated by pull request.


Built by you. Read by your agents.
$ claude mcp add --transport http randr \
https://www.randr.dev/mcp
/mcp → randr → Authenticate
> Use Randr to read the guidelines and
export the design tokens as CSS.OAuth by default, or a personal access token from Settings → Agent access.
Randr is in early access. Workspaces are invite-only, and we set up brand teams one at a time. Pricing comes later, and we’ll tell you well before it starts.
Invite-only during early access. No newsletter.
Not on its own. Agents read the published release through read-only tools. If you grant the opt-in propose scopes, an Editor’s agent can suggest token and guideline changes. They wait under Proposed changes until an Editor accepts, and publishing stays a separate step.
Randr is in early access. Workspaces are invite-only: request access and we’ll set yours up and invite your team. Already invited? Sign in with the address your invitation went to.
Tokens as W3C DTCG JSON, including Tokens Studio and Style Dictionary files, exported as CSS, DTCG or JSON. Assets as PNG, JPEG, WebP, SVG or PDF, up to 25 MiB each.
Only as a pull request from its own branch, in repositories you select. It never pushes to your branch, force-pushes, approves or merges.
You see exactly what would be replaced first. Restoring then creates a new release; earlier ones stay available.
Workspace data and the agent gateway run in Google Cloud’s europe-west6 region in Zürich. Files are delivered through short-lived signed URLs, and every agent request is rate-limited and logged.