Announcement
Token Designer is now Bezel
Token Designer is now Bezel, and the product lives at bezel.new. It’s the same product, built by the same people, doing the same job. What changed is the name. This page explains why we picked a new one, what a bezel has to do with design systems, and what you need to do about it. The answer to that last one is almost nothing.
What changed
The product you know as Token Designer is called Bezel now. The name is different. The team, the roadmap, and the code underneath are not.
Bezel lives at bezel.new. That’s where the product and the documentation are, and it’s where new work happens. Your existing login works there, so signing in is the whole of the transition for most people.
A rename is a small thing to a company and an irritating thing to a customer, so here’s the entire Token Designer rebrand in one line: same product, same team, same login, new name, new address. The rest of this page is the reasoning, in case you want it.
Why “Token Designer” stopped fitting
Token Designer was an accurate name for about a year. It said what the product did on day one, and it said it in the plainest way available. Plain names age well when the product stays where it started. This one didn’t.
The name described a file, not a workflow
A design token is a named value. A color, a spacing step, a radius, a rung on a type scale. Naming the product after the artifact made sense when producing that artifact was the entire job. But nobody wakes up wanting a JSON file. They want a design system that holds together, that they can look at, and that their tools can read without a translation step in the middle.
By the time the product had a live preview, theme generation, contrast guidance, framework exports, a Figma bridge, and an MCP server, “Token Designer” was describing roughly the first tenth of it. People read the name, concluded “token editor”, and never looked at the rest. At that point a name isn’t doing work anymore, it’s doing damage.
It kept us in a category we’d already left
Names set expectations, and expectations set the size of the conversation you get to have. “Token Designer” put us in a conversation about design token file formats. That’s a real conversation and we’re still in it, DTCG format and all. It just isn’t the one worth leading with.
Where this is going is broader than design tokens. It’s the whole system your product is built from, generated and maintained with AI, and reflected back to you as real interface instead of as a diff. There’s no version of “Token Designer” that stretches far enough to cover an AI design system that does that. We could keep explaining past our own name, or we could change it. Explaining past your own name is a tax you pay on every single impression, forever.
What a bezel is, and why the name fits
A bezel is the frame around a screen or a watch face. It’s the ring you look through. It isn’t the content and it isn’t decoration. It’s the thing that holds the view steady so you can see what’s actually there.
The frame around the live preview
The centre of this product is a live preview. You change a token and you watch real components change, in the same moment, wearing your brand. Not a swatch grid. Not a static export you open somewhere else to check. Real interface, redrawn while you work.
A bezel is what surrounds that view. Naming the product after the part people actually spend their time inside is a better idea than naming it after the file it emits.
Live preview is what makes AI edits safe
AI is very good at proposing changes to a design system and very bad at telling you what those changes will look like. Ask a coding assistant to warm up your neutrals or tighten your spacing scale and what comes back is a diff. A diff is not a look. You end up approving a change you can’t see, which is how design systems quietly drift.
Bezel closes that loop. When an AI edit lands, the preview reflects it immediately, on real components, across your themes, at your real contrast ratios. You approve what you can see instead of what you can parse. That’s the entire argument for live preview, and it’s why the frame is the thing worth putting on the door.
The reflection runs the other direction too. You can point the preview at your own product, so you’re not judging a proposed system against generic demo components but against the interface you actually ship. Watching your own screens wear a change is a different level of confidence than watching a button and a card wear it.
A frame doesn’t repaint what’s inside it
The metaphor has a second half, and it matters more than the first. A bezel holds the view. It doesn’t change it. Renaming the product doesn’t change how it works, what it exports, or how your team uses it. Same system. Framed better.
What stays the same
This is the section most people came for, so it’s deliberately boring.
Your login
Your existing account works at bezel.new. Same credentials, no second signup, no verification email to hunt for. Sign in and you’re in.
The product and everything it exports
Token generation, theme generation, the live preview, AA and AAA contrast guidance, the AI assistant, the Figma bridge, and the MCP server all work the way they did. So do the export formats: Tailwind configuration, shadcn/ui theme variables, Mantine overrides, CSS custom properties, and DTCG JSON. Same output, same structure.
Nothing in your prompts, your agent setup, or your build pipeline needs rewriting because of a rename. The tool names and their behavior are unchanged.
The team
Same people, same roadmap, same support inbox. If you were talking to someone here last month, you’re talking to the same person this month.
What to do now
Go to bezel.new
The new site is live. Sign in with the account you already have. If you were partway through evaluating Token Designer, you aren’t starting over.
Update your bookmarks and links
bezel.new is the address to save. If you’ve written about Token Designer, linked to it from a docs site, or referenced it in an internal design system README, updating that link is the only housekeeping we’re asking for.
Bringing an existing project across
If you have work in Token Designer you want in Bezel, get in touch from bezel.new and we’ll handle it with you directly. Mention which project you mean and we’ll take it from there.
Frequently asked questions
Is Token Designer shutting down?
No. Token Designer is Bezel. Same product, same company, a different name. Nothing is being retired and nothing is being sunset.
Do I need to create a new account?
No. Your existing login works at bezel.new. Sign in with the credentials you already have, there’s no separate signup to go through.
Why “Bezel” and not something else?
Because live preview is the centre of the product, and a bezel is the frame you look through. The name had to survive the product growing past design tokens, and it had to describe what using the thing actually feels like. Bezel does both.
Is this the same team?
Yes. Same people, same roadmap, same support. A rename changes the label on the door, not who’s behind it.
What happens to tokendesigner.com?
It stays online. You’ll keep seeing this notice at the top of every page pointing you to Bezel, so any link you’ve already published still leads somewhere useful.
I have an existing Token Designer project. What about it?
Get in touch and we’ll sort it out with you directly. Contact us from bezel.new and mention the project you want brought across.
Where are the docs?
Documentation lives under the Bezel domain now and is linked from bezel.new.
Bezel is live. Go look at it.
The fastest way to understand a rename is to use the thing it renamed. Open bezel.new, describe your brand in a sentence, and watch a full design system land on real components. Your Bezel design system generates the same formats, wired to the same tools, as the one you know. It just has a name that finally fits.