HeroUI Dropped Its Own Name - Then Rebuilt Everything

There is a strange thing that happens when an open-source project gets popular enough. People start depending on it for real work, and the person who built it at night, for fun, wakes up as the accidental steward of something serious. Junior Garcia hit that moment with a React component library he named NextUI. In 2026 it has a different name, a rewrite, a mobile version, and a Y Combinator term sheet behind it. The name it lost tells you as much as the name it kept.

HeroUI is a library of pre-built interface pieces - buttons, cards, modals, tables, date pickers - that React developers drop into their apps instead of building each one from scratch. If you have used a website with a clean, consistent look and interactions that just work, there is a decent chance the developer did not hand-craft every dropdown. They pulled from a library like this one. HeroUI is the library, and it is free to start using.

Why NextUI became HeroUI

The original name was a small trap. NextUI sounded like it belonged to Next.js, the popular React framework owned by Vercel. It did not. The library worked fine with Vite, Remix, and Astro too, and it had no official tie to Vercel at all. The name implied a marriage that never happened, and it kept confusing people. So the team did the unglamorous thing and renamed it. NextUI became HeroUI, and NextUI Pro became HeroUI Pro.

Renaming a project with tens of thousands of stars is not free. Search rankings reset, tutorials go stale, and every "how do I install NextUI" answer on the internet now points at a ghost. The team did it anyway, which tells you they were planning for a longer game than a weekend project usually gets.

What is actually inside the box

HeroUI's pitch rests on two engineering choices most users will never see but will always feel. The first is accessibility. Every component is built on React Aria, Adobe's toolkit for keyboard navigation, screen reader support, and the fiddly details of making software usable by people who do not point and click. In HeroUI, that behavior is the default, not a setting you remember to turn on.

The second is styling. HeroUI uses Tailwind CSS v4 rather than shipping a runtime styling engine that runs in the browser while your app is live. In v3, the team pushed this further: all animations now run on plain CSS, with no JavaScript doing the work of moving things around. One release, v3.0.3, dropped roughly 90% of the library's transitive dependencies - the invisible pile of packages that gets pulled in behind the one you actually installed.

In March 2026 the team shipped HeroUI v3, a ground-up rewrite. It brought the component count on the web past 75, and introduced something new: a React Native library with 37 components. That gives HeroUI a single design system across web and mobile, so the button you build for a website behaves like the button in the phone app. Keeping those two in sync is harder than it sounds, and it is the kind of work that only pays off if you are building for the long haul.

A UI library built for machines

Here is the part that makes HeroUI more than a nicer set of buttons. A growing share of UI code is now written by AI coding assistants - Cursor, Claude, and their cousins. Those tools are only as good as the documentation they can read. HeroUI ships an MCP server, agent skills, and an llms.txt file: machine-readable instructions so an AI assistant can understand the components and write correct code with them, instead of hallucinating props that do not exist.

It is a clear-eyed reading of where the work is heading. When anyone can generate an app from a sentence, the apps that look and feel right are the ones that stand out - and the library the AI reaches for becomes the default look of a lot of software. HeroUI wants to be that default, for the human and for the machine typing next to them.

How free makes money

The core library is free and open-source under the Apache-2.0 license. That is the funnel, not the product. Revenue comes from HeroUI Pro, a paid tier of premium templates - production-ready dashboards, mail, chat, and finance apps - along with installable blocks, design systems, and AI tooling for teams that want to ship faster than free components allow. There is also HeroUI Chat, an AI platform for generating frontends from prompts.

It is the open-core model that has worked for a generation of developer tools: give the useful thing away, sell the thing that saves a team a week. In 2024 the company joined Y Combinator's Summer batch and raised about $500K from YC, Pioneer Fund, and Epakon Capital Management. The team is small - around five to seven people - with roots in Buenos Aires, Argentina.

Where HeroUI sits

The React UI space is crowded and opinionated. HeroUI is not trying to be the biggest; it is trying to be the one that is beautiful by default while staying accessible and light. Here is roughly how the neighborhood looks.

The move to Tailwind v4 puts HeroUI in the same conversation as shadcn/ui for developers who live in Tailwind, while the accessibility-by-default posture and the native library give it ground the copy-paste crowd does not cover.

From side project to YC company

Not every v2 user cheered the rewrite. One developer summed up the honest tension of any ground-up rebuild: "The themes page is pretty and the documentation is bang on as usual, but I keep finding things missing which I loved in v2." That is the cost of betting on a stronger foundation over a longer feature list, and HeroUI made the bet in public, on a monthly release cadence, closing the gaps one version at a time.

What HeroUI is really selling is time. A developer who reaches for it skips weeks of building accessible components by hand, gets a look that holds up, and - increasingly - hands the whole thing to an AI assistant that already knows how the pieces fit. The name changed. The idea got sharper.