Question 1

What’s free, and when does it launch?

Accepted Answer

The 10 free components are rolling out now under MIT, one every couple of days. They stay free, commercial use included.

Question 2

Does it work with my stack?

Accepted Answer

It needs React 19 and motion. React 18 isn’t supported: each part ships its styles through React 19’s stylesheet support. Every file starts with "use client", so the Next.js App Router and Server Components import it like any client component. No Tailwind, provider or config. At launch each part is one command (npx brio-ui add pricing-toggle), with Markdown docs and a line in llms.txt, so Claude Code, Codex or Cursor can add one for you. The sizes on the cards are each file minified and gzipped with its CSS; React and motion are excluded.

Question 3

How does Pro pricing work, and what does “for life” cover?

Accepted Answer

Bought once, no subscription. All access (every Pro component, including later ones) is $149, packs are $39 and singles $9; founding members pay half, so $74.50, $19.50 and $4.50. The 50% covers every Pro purchase you make, packs and singles, including Pro parts released after launch, for as long as Brio sells Pro. It’s tied to the email you join with, and the founding offer closes on Monday 30 November 2026, 23:59 IST. The full terms are at brioui.com/terms.

Question 4

Why not shadcn/ui, Origin UI, Aceternity or Magic UI?

Accepted Answer

Use them too. shadcn/ui and Origin UI give you well-made primitives to build screens from; Aceternity and Magic UI are great at hero effects. Brio covers the everyday working parts in between, like the pricing toggle, the OTP field and the changelog, with the motion and the awkward states already done. It sits next to shadcn/ui without conflict.

Question 5

What’s tested for accessibility and motion?

Accepted Answer

Every part reads prefers-reduced-motion and swaps movement for a short fade or none. Every part works with the keyboard alone and ships its ARIA roles and live announcements. Each one is run keyboard-only and with reduced motion on, in Chromium, before it ships; the worst-case layouts also run in WebKit (Safari’s engine).

Question 6

Can I use it commercially?

Accepted Answer

Yes. The free set is MIT, so paid and client projects are fine. Each part is one file you copy in and then own.

Question 7

Who’s building this, and will it last?

Accepted Answer

Harjot, a solo maker who also built Helicon, an unofficial open-source desktop app for Meta’s Muse Code CLI. Every part is a single file you copy into your own code, so your copy keeps working whatever happens to Brio.

Question 8

What happens after I join?

Accepted Answer

A welcome email arrives right away with your member number and an “Open your pass” link, which confirms your address; you’re on the list either way. After that, two emails: launch day with the free set, and Pro early access. Your pass has a link to share: a friend counts once they open their own pass from their welcome email, and at three you pick any $9 Pro single free, to redeem when Pro is available. Unsubscribe any time.

Brio UI: Everyday React components. Edge cases handled. Done with brio.

Security and billing

Break it before you install it

Try the 10 free components.

Tested where kits break.

Every width

Long strings

Right to left

Messy text

Slow CPUs

Keyboard only

Before you join.

Join before launch.
Pay half for Pro, forever.