The origins of Sora UI, how it diverged from Animate UI, and where it is headed.
Origins
Sora UI started as a fork of Animate UI by @imskyleen. The initial codebase, registry conventions, and copy-paste distribution model came from that project.
Since then, the architecture, registry system, component APIs, and motion primitives have been substantially redesigned. Some patterns and abstractions still trace back to the original codebase.
Direction
Sora UI is being built toward an AI-native UI ecosystem — its own registry architecture, AI-assisted tooling via an MCP server, and a component roadmap built around motion-first, composable primitives.
What's different from upstream:
- AI-native tooling — an MCP server that lets AI assistants search docs, browse the registry, and install components
- Three-tier primitives — Motion, UI, and Catalog as distinct layers of abstraction
- Multi-primitive support — components ported across Radix UI, Base UI, and Headless UI
- Deeper motion system — accessible defaults, reduced-motion support, and composable animation primitives
License & attribution
Sora UI is distributed under MIT + Commons Clause, the same terms as Animate UI.
The upstream copyright notice:
Portions Copyright (c) 2025 Elliot Sutton (Animate UI — https://github.com/animate-ui/animate-ui)
Full license text on the License page.
Questions
If something looks like it's missing credit, reach out.
Built by Axyl. A motion-first component registry for React.
Last updated: 9/10/2026