Background
The story behind FivFold—from production scaffolding needs to a full-stack Kit platform.
FivFold did not appear overnight. Its roots trace back to Fivex Labs, a product development studio that needed out-of-the-box scaffolding for production builds. What followed was a journey through the React UI ecosystem, a custom solution, and ultimately the platform you see today.
Origins
The idea behind FivFold started when Fivex Labs wanted a production-ready scaffolding kit—something that could accelerate client projects without reinventing the wheel. At the time, shadcn/ui was leading the market for React-based platforms. It offered copy-paste components, a clean design language, and strong adoption. But that dominance came with a dependency: Radix UI.
The problem
shadcn/ui was built on Radix UI primitives. When WorkOS (the company behind Radix UI) stopped supporting those primitives, the ecosystem stalled. shadcn/ui went a long time without updates. On top of that, Fivex Labs routinely needed components that simply were not available—more than what shadcn/ui offered out of the box.
Stale primitives
With Radix UI support withdrawn, shadcn/ui components could not evolve. Security fixes, accessibility improvements, and new patterns were delayed or blocked.
Gap in coverage
Daily production work required components beyond shadcn/ui's scope. Building them from scratch or gluing third-party libraries added friction and inconsistency.
FivUI
In response, the team at Fivex Labs built their own registry and component library: FivUI. It supported multiple baseline primitives—Radix UI, Base UI, and Ark UI—so projects were not locked to a single vendor. FivUI also shipped a theme generator, featured themes, and more components than shadcn/ui out of the box. It became the default choice for Fivex Labs projects.
What FivUI delivered
A flexible registry, multi-primitive support (Radix, Base, Ark), a theme generator, curated themes, and a broader component set. FivUI filled the gaps left by a stalled shadcn/ui.
The pivot
When shadcn/ui eventually received updates—new features, a refreshed design language, and renewed momentum—the calculus changed. FivUI was no longer adding unique value. Maintaining a parallel component library that duplicated shadcn/ui did not serve the community. The right move was to evolve, not compete.
Evolve, not compete
From components to Kits
Deprecation
FivUI is deprecated. If you run the legacy FivUI CLI, you will see a message directing you to FivFold. We recommend migrating to FivFold for new projects and future updates.
Today
FivFold is the evolution of that journey: a full-stack Kit platform that embraces shadcn/ui, adds production-ready scaffolding, and keeps the code in your hands. Built by Fivex Labs, for teams that ship.
Under the hood
FivFold uses a Virtual File System (VFS)—all changes are staged in memory and committed atomically. A Strategy Pattern composes interchangeable generators. Kits are defined by manifest-driven JSON schemas, not hardcoded permutations. See the How it works section for architecture details.
Fivex Labs
Learn more about the team behind FivFold