Recommended libraries
Runqora only builds screens nobody else does. These shadcn registries cover the rest, and each one installs with the same CLI. We aren't affiliated with any of them.
Each registry is in the shadcn directory, so you can list what it offers by its namespace:
npx shadcn@latest search @diceuiAuth and accounts
Sign-in, account settings and everything around users.
Better Auth UI(opens in a new tab)
Per-style buildsSign-in and sign-up forms, account settings, organizations, API keys and admin user management for Better Auth.
If you use Better Auth, it covers the account screens, so Runqora doesn't.
@better-auth-ui
Billing
Pricing, plans and what a customer pays.
Pricing tables, subscription management, usage meters and invoice history for SaaS billing.
The most complete set of billing screens in the directory.
@billingsdk
Uploads
Getting files into a bucket. Pair one with Runqora's file browser to manage them afterwards.
UploadCN(opens in a new tab)
Per-style buildsDropzones, upload queues and resumable uploads to S3 and R2, with blocks for every style.
Covers large and resumable uploads that the file browser's upload button leaves out.
@uploadcnDirect uploads from the browser to any S3-compatible service, with a small server route you own.
A lighter option when you only need an upload field.
@better-upload
Building blocks
Components shadcn/ui doesn't ship, to build your own screens.
Dice UI(opens in a new tab)
Per-style buildsAccessible components such as a data table, kanban board, sortable lists, tags input and mentions.
Runqora's audit log viewer and webhook delivery log install its faceted filter and relative-time card.
@diceuiData tables with faceted filters, sorting, infinite scroll, a row detail sheet and server-side data.
A good starting point for log and admin tables over large data sets.
@data-table-filtersReUI(opens in a new tab)
Per-style buildsA large library of components and patterns for shadcn projects.
Worth checking before you build a pattern from scratch.
@reui
Status and onboarding
Telling customers what's going on.
Components for building status pages.
From the team behind the open-source OpenStatus monitoring service.
@openstatusOnboarding tours that point new users at parts of your app.
A small, focused component for first-run walkthroughs.
@tour
Know a registry that belongs here? Open an issue.