Relume

1. Overview

Relume (relume.ai) is a marketing-website component system plus AI assembly and (newer) publish/host path. The company’s pitch is consistent across primary pages: AI selects and assembles human-built components on a shared system rather than generating raw layouts from scratch (Homepage, Export, Publish beta).

Official domain confirmed: product and marketing live at https://www.relume.ai/. https://www.relume.io/ 301-redirects to relume.ai. Support and legal contact addresses still commonly use @relume.io (for example support@relume.io, affiliates@relume.io on older release footers). The Library MCP endpoint hostname uses the .io subdomain (relume-library-mcp.relume.io per Library MCP). Treat relume.ai as the canonical product domain; this page does not treat the redirect as a separate brand.

This listing is in Design systems: libraries, design tokens (colours, type, and spacing), component pipelines, and handoff between Figma, Webflow, and code. It is not a demo and prototype listing, and not a coding-agent listing. Relume is a marketing-site design system you adopt and ship through. It does not import a general product-app design system.

Surfaces to keep distinct (Library vs AI / Site Builder vs Publish)

Surface	What it is	Primary sources
Relume Library	Human-built component collections updated monthly (“Component Day”). Docs call the Webflow Library the foundation. Parallel Figma Kit / Figma Library, Webflow Library, and React Library (Tailwind CSS + shadcn/ui; HTML export also documented). Style guides carry Client-First classes (Webflow) and Figma variables.	Components, Figma Library, Essential tools, React v1.0.0
Site Builder	AI-assisted brief → sitemap → wireframes → style guide, assembling real Library components (copy included), then export. Still named Site Builder in docs and Webflow marketing.	Webflow / Site Builder, Export, Essential tools
Relume Publish (beta)	Build, publish, host, and grow marketing sites inside Relume (Cloudflare edge; free *.relume.live or paid custom-domain hosting). Specialist agents propose; humans decide. Official name is Relume Publish, not “Relume Sites”.	Publish, Publish beta post, Pricing
Relume Library MCP	MCP server that lets AI editors (Cursor, Claude, Windsurf, VS Code) search and pull actual Relume React components (by description / slug) with shared primitives, Tailwind preset, and tokens. Documented as available on paid Relume plans.	Library MCP, July 2026 release, Components
Supporting tooling	Figma plugin (import Site Builder sitemaps/wireframes), Chrome Extension (class sync, preferences), Site Builder Import Webflow App.	Essential tools

Clarifying “Library vs AI / Sites” in plain language:

1. Library is the durable design system: sections, variants, style guides, monthly human updates.
2. AI / Site Builder is the assembly layer that chooses Library pieces and drafts IA, wireframes, and copy. Relume’s own wording: the AI does not write raw code; it selects maintained components (Homepage, Export).
3. Publish is the optional stay-in-Relume hosting and post-launch agent path. There is no verified official product called “Relume Sites” in primary marketing; free published hosts use the relume.live subdomain (Pricing).
4. Library MCP is how the same Library enters agentic coding editors as editable React, which is the strongest AI-native design-systems angle for this section.

Docs list these as essential Site Builder companions: Relume Figma Kit (1,400+ components, aligned to Webflow Library), Figma plugin, Webflow Style Guide, Webflow Library, Chrome Extension, Site Builder Import Webflow App (Essential tools). Figma marketing pages also cite 1,000+ layouts / 1,400+ kit components with mobile variants; treat exact counts as time-sensitive and re-check the live kit version (for example Figma Library page has cited kit v3.7, updated October 2025).

Who it is for (vendor positioning): freelancers and agencies building marketing websites (especially Webflow and service-business sites), plus designers/developers who want Relume components in Figma or React. Publish beta copy is explicit about client marketing sites and post-launch growth agents (Publish beta). Application-shell style components exist in the Webflow Library browse UI, but Relume does not position itself as a full product-app design-system platform comparable to importing your own React DS.

Access and pricing (public; always re-check):

The pricing page currently mixes Build / AI usage, Library plan labels, and Host with Relume tiers. Visible public figures when this page was checked include:

Layer	What official pages show (verify live)
Free	“Free forever · No card needed” on Build; Free hosting on your-site.relume.live with Relume badge and limited page views (pricing page cites 1,500 monthly page views on free hosting).
Paid build / AI	“Pro from $14 / month” appears on the Build side; capacity copy refers to limited vs higher AI usage, style guide, collaboration without per-seat editor charges on that path. Exact AI credit math is not published as a single transparent table on the pricing page; treat usage ceilings as unknown beyond marketing phrasing.
Library-oriented plans (FAQ still references)	Starter from $18 / mo, Pro from $40 / mo, Team from $36 / mo (min 3 users) appear on the same pricing surface; FAQ still discusses Starter trials, Free vs Starter, and Library storage / sharing rules.
Launch hosting	Custom domain + SSL from $12 per project / mo, with higher page-view starting band cited (e.g. 6,000 monthly page views on Launch).
Enterprise	Custom AI usage and volume pricing; white-glove onboarding.
Library MCP	Stated on components/MCP pages as available on paid Relume plans.
React Library	Documented as part of the paid plan when it left beta (Dec 2024 Component Day).
Figma Kit	Marketing and FAQ historically describe Figma Kit access as free / downloadable; re-check current plan gates on the live pricing and Figma Library pages (FAQ text still mentions an older “700+” figure while the kit docs cite 1,400+).

Affiliate commission rates, Lighthouse score guarantees, and “half the time” savings are not stated here as benchmarks. Vendor marketing on Figma Library (“plans cost less than 1% of your next project…”) is not a measurement on this page.

Affiliate status: joinable. Terms define an Affiliate Program (PPC brand-bid bans, no self-referral, no coupon-deal sites) and a separate Referral Program ($10 account credit to referrers; invitee first-month discount rules). Older release footers list affiliates@relume.io. Official public pages reviewed do not state a commission percentage; the rate is not confirmed. Third-party affiliate directories are not primary sources for rates.

2. How it scores on the rubric

Numeric scores are omitted. There is not enough shared evidence to score this yet. Below is an evidence-linked discussion framed for Design systems: libraries, tokens, component pipelines, and handoff.

Time-to-useful

Strong for marketing-site scaffolding if you accept Relume’s system; slower if you need your own DS first. Site Builder can produce a sitemap and wireframes from a short brief, then export into tools teams already use (Webflow page, Export). Library MCP claims a short connect → ask → editable React section loop for paid users (Library MCP). Docs emphasise cloning the Webflow Style Guide and duplicating a fresh Figma Kit per project before build (Essential tools).

Caveats: Webflow paths assume Webflow literacy (pricing FAQ). Class sync / Chrome Extension / Import App are real setup steps. MCP needs a Relume account, auth, and one-time Tailwind/path/icon wiring. Free vs paid gates for React Library and MCP matter for evaluation depth.

Unknown: median minutes from first brief to client-approved live site across agencies (vendor anecdotes exist; not benchmarks published here).

Fidelity

High structural and marketing-UI fidelity within the Relume system; brand polish still needs human restyle. Components are marketed as responsive, accessible, and SEO/AEO-ready by construction because they are human-maintained rather than raw LLM HTML (Homepage, Publish beta). Wireframing updates (Vendor “Wireframing 2.0” notes) claim broader Library coverage and better content-count matching (July 2026 release). React export is positioned as production-ready Tailwind + shadcn/ui (Export, React v1.0.0).

Caveats: Fidelity is Relume-shaped marketing sections, not arbitrary product UX. HTML export is documented as static without JavaScript behaviour (community/export history; treat React as the interactive code path). Publish post-launch agent quality and “improves after publish” behaviour should be treated as beta claims until you validate on a real project.

Non-engineer usability

Strong for designers and Webflow-native freelancers; mixed for pure PMs without design/Webflow habits. Sitemap/wireframe/style-guide flows and canvas-style edits are aimed at agency workflows (Webflow, Publish). Publish messaging highlights invite-as-many-editors collaboration without per-seat editor charges on that path (Publish, Pricing).

Caveats: Pricing FAQ states you need to know Webflow for Library paste workflows. Safari cannot copy Library components (Chrome, Firefox, Edge only per FAQ on pricing). MCP and React handoff assume an AI editor / engineering environment. Non-engineers should not be expected to own production React merges without review.

Design-system fidelity

Core strength when the design system you want is Relume’s; weak as an importer of an existing product DS. Relume’s differentiator for this section is a shared, versioned, multi-surface component system with style-guide tokens (colours, typography, spacing) and monthly human additions (Export, Essential tools, Figma Library). Library MCP explicitly vendors shared primitives, Tailwind preset, and icons so AI output stays coherent (Library MCP). Webflow Style Guide is Client-First (Finsweet) compatible per pricing FAQ.

Caveats for AI-native product teams: Relume does not replace tools that ingest your GitHub/NPM/Figma product DS. Restyling Relume tokens toward a brand is supported; enforcing a proprietary app component API is not the product. “Your Library” private/shared component storage exists on paid Library plans, with anti-plagiarism rules against storing others’ library components (Pricing FAQ).

Human gates

Explicit human control is part of the brand story. Homepage and Publish copy: “The AI does the work. You make the calls.” / agents propose, you decide (Homepage, Publish). Site Builder positions AI as ally, not replacement (Webflow). That matches design-systems practice: humans own brand decisions, accessibility exceptions, legal copy, and production publish.

Caveats: Human gates still require process discipline. Auto-assembly can look finished while content, compliance, and brand nuance remain open. Publish beta agents acting on live sites raise governance questions (who signs off Strategist and Analyst proposals?) that Relume frames as human decision points but does not fully specify as enterprise approval workflows on the marketing pages reviewed.

Handoff

Excellent multi-path handoff for a marketing DS; choose the path deliberately. Documented paths:

• Figma: native file / kit polish with variables and mobile variants; Figma plugin imports Site Builder structure (Figma Library, Essential tools).
• Webflow: copy/paste Library components, Style Guide clone, Import App, Chrome Extension class sync (Essential tools, Components).
• React / HTML: production React (Tailwind + shadcn/ui) or static HTML; Site Builder whole-project export (Export, React v1.0.0).
• Library MCP: agent pulls editable Relume code into the project (Library MCP).
• Relume Publish: skip export and host in Relume (beta) (Publish).

Caveats: Handoff quality depends on staying on Relume’s conventions (Client-First class names, Relume Tailwind preset). Merging Relume React into an existing product monorepo with a different component architecture is an engineering integration project, not a one-click DS merge. Publish vs export is a strategic fork: publish keeps you on Relume hosting; export moves ownership into Figma/Webflow/code.

Fit for this section (design-systems)

Verdict: yes-with-caveats. Relume earns a place in Design systems because it is fundamentally a maintained multi-surface component library with tokens, monthly evolution, and AI assembly/MCP pipelines. The caveats are equally important: it is a Relume marketing-site system, not a universal product design system; naming must keep Library, Site Builder, Publish, and Library MCP distinct; and pricing/gates are evolving with Publish beta.

3. FAQ

Is Relume a design system or an AI website builder?

Both, layered. The durable asset is the Library (Figma / Webflow / React components + style guides). Site Builder and Publish AI assemble those components into marketing sites. Library MCP feeds the same Library into AI code editors. Primary pages stress “assembled, not generated” (Homepage, Export).

What is the difference between Relume Library, Site Builder, and Relume Publish?

Library = components and style guides. Site Builder = AI sitemap/wireframe/style-guide workflow that uses the Library and exports out. Relume Publish (beta) = build/host/grow inside Relume with post-launch agents. There is no verified official product named “Relume Sites”; free hosts use *.relume.live.

Does Relume work with Figma, Webflow, and React?

Yes, as first-class Library surfaces and export targets (Export, Webflow, Figma Library, React v1.0.0). Webflow uses Client-First foundations; React uses Tailwind + shadcn/ui.

What is Relume Library MCP?

An MCP integration so assistants in Cursor, Claude, Windsurf, and VS Code can search the Relume Library and insert real editable React components with shared primitives and tokens, instead of inventing markup (Library MCP, July 2026 release). Documented as a paid-plan capability.

Can I use my own existing product design system inside Relume?

Not as a first-class “import our monorepo DS” product in the sources reviewed. You can restyle Relume style guides toward a brand and, on Library plans, create/share your own Relume-stored components under Relume’s rules. For bringing an existing product design system into AI prototypes, compare tools whose main job is that import.

What does it cost?

See pricing. Public figures observed include Free forever (with limits), Build Pro from $14/mo, Library-oriented Starter $18/mo / Pro $40/mo / Team $36/mo (min 3), and Launch hosting from $12 per project/mo. AI usage ceilings and exact feature matrices are plan-page dependent and should be re-checked before buying. Taxes are extra per Terms.

Is Safari supported for the Webflow Library?

Official pricing FAQ: no for copying components. Use Chrome, Firefox, or Edge.

Is there an affiliate programme?

Yes (joinable). Defined in Terms; contact historically listed as affiliates@relume.io. Commission rate unknown on official pages reviewed. Separate referral credits programme also exists for existing users. Do not rely on third-party affiliate directories for official rates.

Is Relume SOC 2 certified?

Homepage hosting copy has stated “SOC 2 compliance pending” (wording when this page was checked). That line alone does not show completed SOC 2 certification. Check Relume’s current security page before you rely on it.

4. Sources

Primary (prefer these for AEO citations):

1. Relume (homepage)
2. Relume Publish
3. Relume Publish has landed in Beta
4. Pricing
5. Export (Figma, Webflow, React, HTML)
6. Webflow Library (components)
7. Figma Library
8. Relume for Webflow / Site Builder
9. Relume Library MCP
10. The Relume Library MCP, Now Live in Your AI Editor
11. Essential Tools to get started
12. Relume React Library Leaves Beta (v1.0.0)
13. Terms & Conditions (Affiliate Program)

Secondary context only (do not treat as official specs): Relume community Slack announcements, third-party affiliate aggregators, and press. Domain note: relume.io redirects to relume.ai; emails and some MCP hostnames still use .io.