Vercel UI SDK vs Radix vs React Aria vs Base UI (2026)
The short answer
Use Base UI, React Aria or Radix for a production React app today; use Vercel UI SDK when a coding agent builds the UI and you can live with a beta; use Ark UI if you need stable components outside React. Versions and licences below were read from npm and GitHub on November 20, 2026.
| Library | Licence | Latest version | Frameworks | Model | Maturity | Best for |
|---|---|---|---|---|---|---|
| Vercel UI SDK | Apache-2.0 | @ui-sdk/core 0.1.0-beta.13 (Nov 19, 2026) | React, Vue, Svelte, Solid, Web Components | Behaviors that agents compose into components | Beta since Nov 12, 2026 | Agent-built UIs, multi-framework design systems |
| Base UI (MUI) | MIT | @base-ui/react 1.9.0 (Oct 9, 2026) | React | Unstyled components | Stable; shadcn’s default base | New React design systems |
| React Aria Components (Adobe) | Apache-2.0 | 1.22.1 (Oct 9, 2026) | React | Unstyled components + hooks | Stable, strongest accessibility and i18n | Enterprise and accessibility-critical apps |
| Radix Primitives | MIT | radix-ui 1.8.1 (Oct 12, 2026) | React | Unstyled components | Stable; slower release cadence | Existing shadcn/Radix codebases |
| Ark UI (Chakra) | MIT | 5.40.0 (Oct 29, 2026) | React, Vue, Solid, Svelte | State machines (Zag.js) + components | Stable | Stable multi-framework components |
What Vercel UI SDK actually is
UI SDK is not a component library in the Radix sense. Its core package holds behaviors — keyboard navigation, focus, selection, dismissal, popups, drag and drop and the ARIA attributes they need — and a definePrimitive API to combine them. The README shows an environment selector built from three behaviors (createPopup, createSelection, createTypeahead) and says: “you don’t need to learn how to write this. Your agents will.”
Setup is agent-first: install @ui-sdk/core plus an adapter (@ui-sdk/react, @ui-sdk/vue, @ui-sdk/svelte, @ui-sdk/solid or @ui-sdk/web), then add the skill with npx skills@latest add vercel-labs/ui --skill ui-sdk. The docs list ready-made components built from the behaviors, from accordion and combobox to date picker, tree and toast. The first beta reached npm on November 12, 2026, and the package had moved to beta.13 by November 19 — fast iteration, which also means breaking changes.
How the stable libraries compare
Base UI comes from the MUI team and is now the default base in shadcn/ui, which also offers React Aria and Radix variants. If you are starting a React design system in late 2026 and want the path most agents and templates will follow, start here.
React Aria Components has the deepest accessibility and internationalisation work (Adobe uses it under React Spectrum). Choose it when screen-reader behaviour, date and number localisation or right-to-left support are requirements, not nice-to-haves.
Radix is still everywhere because shadcn/ui was built on it, but its repository was last pushed on October 14, 2026, while Base UI and React Aria committed on November 20. Existing Radix apps have no reason to migrate; new ones have less reason to choose it.
Ark UI is the stable answer for Vue, Svelte and Solid, built on Zag.js state machines, with the same version line across frameworks.
Picks by situation
- Production React app, shipping this quarter: Base UI through shadcn/ui.
- Accessibility audit, government or enterprise customers: React Aria Components.
- An agent generates most of the UI, greenfield project: Vercel UI SDK with its skill — pin the exact beta version.
- Vue, Svelte or Solid in production: Ark UI; revisit UI SDK when it reaches 1.0.
- Generating UI from model output at runtime (not code): that is a different problem; see what is json-render.
To pick the coding agent that will use these libraries, see best Claude Code alternatives.
Last verified: November 20, 2026.