Sora UI is an animated component registry for React and Next.js. It ships copy-paste primitives built on Motion, with live docs, demos, and a shadcn-compatible install flow so you can add polished UI effects directly into your project.

Initialize shadcn/ui in your app, then run the add command with the Sora UI registry scope—for example, npx shadcn@latest add @soralabs/accordion. The CLI copies the source into your project so you own and can customize every file.

Yes. Components are added as source files in your codebase, not as an opaque npm package. Tweak Tailwind classes, variants, and tokens to match your design system. Primitives also expose CVA variant helpers you can extend.

Sora UI is built on Motion (motion/react). Timelines, springs, and layout animations are composed with Motion APIs. Wrap your app in MotionConfig with reducedMotion set to user for accessible defaults.

Yes. Components respect prefers-reduced-motion via Motion and useReducedMotion where needed. Interactive primitives handle keyboard focus and ARIA. The docs spell out what each one does when motion is reduced.

Yes. Every primitive in the docs is open to preview and install. Copy the source into your project, customize it, and ship—no account required to get started with real Sora UI code in your codebase.

Each primitive has a registry item with source paths, dependencies, and install targets. Docs previews load demo components from the same registry, so what you see in the docs matches what the CLI installs into components/sora-ui.

Yes. Sora UI is built for production client work. Install components into your projects, customize them, and ship. The only limit is repackaging or reselling the components as a competing library.