Orvain UI vs shadcn/ui
shadcn/ui is the default choice for a React project that wants owned, Tailwind-styled components and nothing else to manage. Orvain UI suits teams that also need a Figma library matching the code, Vue alongside React, and an MCP server their AI tools can query.
Where Orvain is today#
What shadcn/ui is#
shadcn/ui is a collection of accessible React components you copy into your own repository rather than install as a dependency. A CLI writes the source into your project, and from that moment the files are yours to edit: there is no package to upgrade and no abstraction between you and the markup.
It is free and MIT-licensed, styled with Tailwind, and built on top of established headless primitives. It is the most widely adopted approach of its kind by a considerable distance, which means an enormous amount of community work, examples and answers already exists around it.
The differences#
How you get the code
shadcn/ui
A CLI copies component source into your repository. No runtime dependency and no upgrade path: the files are yours from the first minute.
Orvain UI
The same idea for the full library: npx @orvain/cli add flat-button writes the source into your project, and it is yours to keep. The free components also install from npm as @orvain/react or @orvain/vue.
Frameworks
shadcn/ui
React, officially. Ports to other frameworks exist and are maintained by the community rather than by the project.
Orvain UI
React and Vue are both first-class targets, built from one shared contract rather than one being a translation of the other.
Design file
shadcn/ui
No official Figma library. Community kits exist and are not kept in step with the code by the project itself.
Orvain UI
An official Figma library ships alongside the code, and the props and token names are the same on both sides by construction rather than by discipline.
What an AI assistant reads
shadcn/ui
Whatever it absorbed during training, plus whatever you paste into the prompt. It is very widely represented in training data, which helps, but that is still a snapshot.
Orvain UI
A hosted MCP server at mcp.orvain.dev: the assistant queries the real props, variants and tokens for the version you have instead of recalling them from training data. It needs a licence key.
Cost
shadcn/ui
Free, MIT.
Orvain UI
A free component set plus paid tiers. If cost is the deciding factor, shadcn/ui wins it outright.
Maturity
shadcn/ui
Years of production use, an enormous community, and an answer to almost any question already written down somewhere.
Orvain UI
New. The code library and the MCP server launched on 20 October 2026, so there are no years of production use to point to. That is a real difference and it is not in our favour.
Which to choose#
Choose shadcn/ui if
- You are building in React and have no Figma file to keep in step with.
- Cost matters more than anything else on this page.
- You want the largest possible pool of existing examples, answers and community components.
- You need it today, in production, with no unknowns.
Choose Orvain UI if
- Designers and engineers are both working from one system and the drift between the file and the code is costing you real time.
- You ship React and Vue and do not want two libraries that diverge.
- You expect AI assistants to write against your components, and want them reading the real API rather than guessing.
Questions#
Is Orvain UI a fork of shadcn/ui?
No. Orvain UI is not a fork of shadcn/ui; its components are built independently. The two share one idea, that you should end up owning the component source rather than depending on a package, and shadcn/ui is what popularised it. Everything else differs: Vue is a first-class target rather than a community port, and the Figma library is maintained as part of the system rather than alongside it.
Can I use both in the same project?
Yes, Orvain UI and shadcn/ui can sit in the same project. Both give you plain source files in your own repository, so there is no dependency conflict to resolve and no runtime to reconcile. The cost of mixing them is stylistic: two sets of components mean two sets of naming and token conventions, and reconciling those tends to be more work than picking one.
