Brilliant vs Framer

Framer is one of the most impressive products in this space, and the comparison only works if you start by admitting what it is. Framer is an AI website builder. You design, you publish, and what comes out the other end is a live site running on Framer's own infrastructure, with a CMS, SEO controls, and performance services Framer manages for you. Its own headline calls it "the design agent for every step from idea to launch." If a hosted, published website is the thing you want, Framer is very good at delivering exactly that, and this page is not going to pretend otherwise.

Brilliant is a different kind of tool. It's a professional 2D vector design tool, in the Figma mold, whose output is your own files on your own disk. Auto layout, components and instances, vector editing, boolean operations, design tokens, typography, shaders. What you make is a plain-text design file you own, not a site Framer hosts. The two tools point in different directions, and the honest way to choose between them is to know which direction you need.

Framer facts on this page are current as of August 2026. Framer moves fast; where a detail matters, check it against Framer's own docs.

Design that publishes a site, versus design that hands you files

Framer's great strength is also the line where the two tools part. A Framer project is a hosted website, not a file you can take with you. Framer states this plainly on its own help page about exporting, and the wording is worth reading directly:

"Framer does not offer HTML export for self-hosting."

The reason is architectural, and again in Framer's words: many of its "performance and optimization features rely on backend services running on Framer's infrastructure," and "These services cannot be replicated through a simple HTML export." Framer even names the person it's the wrong tool for:

"If you require complete control over hosting infrastructure or need to export source code, Framer may not be the right solution for that workflow."

That's a fair and clear statement of a real boundary, not a knock. If you want a hosted site, the boundary never bites. If you want the artifact, it's the whole story.

Brilliant is built for the artifact. A workspace is a folder on your disk. Each canvas is a plain-text Blueprint file ending in .bl, and Brilliant exports to ten formats, including HTML in three flavors and React JSX, when you want code out. Nothing leaves your machine until you choose to publish. Your designs live where your code lives →

Your designs, your disk, your git

Framer keeps your project in its cloud, versioned by a hosted Branching feature. Branching is a genuine strength and worth naming: you can work a change on a branch and merge it back. But it's a hosted concept, not Git, and there's no plain-text file underneath it to diff.

Brilliant files are plain-text Blueprint on your local disk. They end in .bl, and they diff cleanly in git. Branch a canvas to try a direction. Commit the experiment. Revert it if it doesn't work out. Run git blame to find the commit where the hero color drifted off-brand. Every primitive your codebase already uses is now available for your designs:

 c16fc75741feed85 fr p(80,80) s(480,320) rd(16) "Hero"
-  88625e475868c087 r p(24,24) s(160,100) f[(r1,#F8F8F8)] rd(8) "Panel"
+  88625e475868c087 r p(24,24) s(160,100) f[(r1,#0080FF)] rd(8) "Panel"

Blueprint is an open, documented, versioned language with a formal spec. And a published Brilliant project is itself a real Git repository with a clone URL, so "GitHub for design" isn't a metaphor here.

Agents: an open protocol, versus a bridge Framer built on purpose

Both tools are built around agents now, and here the designs diverge in a way worth stating precisely rather than scoring.

Framer chose not to ship MCP. It built a proprietary bridge instead, the @framer/agent package, and it says so directly:

"It works differently from MCP under the hood, but it gives you the same functionality an MCP server would, done better."

External agents like Claude Code and Codex connect through that package and reach the same capabilities as Framer's built-in agent, though Framer notes trade-offs in real-time streaming and canvas-context awareness, and its docs steer external agents toward one-off edits rather than sustained design work. Framer's agents also reach well past the canvas, into CMS, analytics, domains, and DNS, which is a wider operational surface than a design tool's agent has any reason to touch. That reach is real, and you should weigh it.

Brilliant runs a standard local MCP server at http://127.0.0.1:3333/mcp the whole time the app is open, documented for Claude Code, Claude Desktop, Cursor, Codex, Copilot, Windsurf, and Antigravity, plus Gemini CLI, Zed, and OpenCode. It's unlimited on every plan, including Free. An external agent drives the same canvas commands you do, over a hundred of them, each with full undo, and everything it makes lands as real, hand-editable vector elements. Whether you prefer a vendor's bridge or an open protocol is a genuine choice; Brilliant's bet is the open one, stated without calling Framer's the wrong one.

And the model is yours. Brilliant is bring-your-own-key: Anthropic, OpenAI, Google, OpenRouter, a Claude Code or Codex subscription, or a local endpoint through LM Studio, Ollama, or vLLM. Brilliant hosts no inference and takes no markup. Framer's AI is metered in Framer credits per plan, with no bring-your-own-key option documented, and the free tier's credits are a one-time allocation rather than a monthly refresh. Bring your own key →

A design system, not three Style types

Framer's token layer is Styles, and there are three of them: Color, Text, and Link, with a two-value Light and Dark axis on color. It's clean and it covers the common case. What it isn't is a general token system with numeric scales or multiple modes.

Brilliant compiles a Styles/*.ds source into a full design system: eleven-step OKLCH color ramps from a single seed, light and dark theming, modes as transforms, multi-brand overlays, and a cascade across folders. The resolved output is a .gen.yaml that Style Dictionary and Tokens Studio can read, so the tokens your designers set are the tokens your build reads. How the token system works →

What Brilliant has that Framer doesn't

• Your files, on your disk. Plain-text Blueprint that diffs in git, exported to ten formats including HTML and React. No hosted-only lock-in.

• A standard MCP server, unlimited on Free. An open protocol any MCP client can drive, not a proprietary bridge, and no credit meter on agent access.

• Bring your own AI key, zero markup. Anthropic, OpenAI, Google, OpenRouter, local endpoints, or a Claude Code and Codex subscription. Framer meters AI in its own credits.

• A full design-token system. OKLCH ramps, modes, brands, and a resolved file Style Dictionary and Tokens Studio read. Framer stops at three Style types.

• Native GPU shaders as first-class fills. Metaballs, metal, iridescent, steel, composed with your effects and exported to raster or video.

• A desktop app on macOS, Windows, and Linux with your work on local disk, not a browser tab over someone else's servers.

What Framer has that Brilliant doesn't

Framer is strong, and several of these are things Brilliant simply does not do.

• A published, hosted website as the output. CMS, SEO controls, and Framer-managed performance services, with an uptime guarantee on Enterprise. Brilliant produces design files and code, not a live hosted site, and has no equivalent.

• Interactive prototyping and production motion. Framer's Motion runtime does hover and drag gestures, scroll effects, parallax, and page transitions. Brilliant is a static canvas today, with no interactive prototyping at all.

• Real breakpoint-based responsive design. Three named breakpoints, Desktop, Tablet, and Mobile, with per-breakpoint text styles.

• Agents that reach past the canvas into CMS, analytics, domains, and DNS, a wider operational surface than Brilliant's canvas agents.

• Shaders that accept video and play in realtime while you edit their properties.

• A built-in code editor for React code components that render live on the canvas and the published site.

If a hosted site with a CMS, or clickable prototypes, is the thing you can't ship without, Framer is the right call for that workflow.

At a glance

A new dance

Framer and Brilliant aren't really the same product with different prices. Framer turns a design into a hosted site and manages everything under it. Brilliant turns a design into files you own and hands them to you, agents included. If you're shipping a website and want the hosting handled, Framer is a fine answer. If you want the artifact, in git, drivable by an open protocol, with the AI bill in your own name, that's the tool Brilliant is trying to be.

Read the full manifesto to see the rest of the argument, or install Brilliant and try it for yourself.