Templates
Full-page Templates
A one page pre-launch waitlist: animated screenshot wallpaper, a signup form with bot screening and rate limiting, and full SEO metadata.
A Laravel and Inertia commerce admin on a real Eloquent backend: orders, catalog, customers, inventory, promotions and analytics.
A commerce admin on TanStack Start: orders, catalog, inventory with purchase orders, customers, promotions, reviews and analytics.
A general purpose Next.js admin: user directory, roles and permissions, access requests, an audit log, products, billing, a deal board and reports.
A Next.js sales CRM: deal board, forecast, quotes and approvals, contacts and companies, with reports and a full settings area.
Directory, reporting tree, leave calendar, timesheets, hiring board and approvals, running on Laravel 13 with Eloquent tables behind every write.
An AI agent operations console: run queue and step traces, an approval queue, a tool matrix, eval regressions, provider routing and token spend.
A task management dashboard on TanStack Start, nine pages over a typed mock layer, with a test suite covering the flows it ships.
A React people operations console: a directory nested by reporting line, time off, timesheets, a hiring board and approvals, on a typed seed with no backend.
A DevOps delivery console on TanStack Start: pipelines, deployments, a service catalog, metrics, logs, traces, alerts, incidents and an on-call rota.
Shadcn UI templates, built from components and blocks
A ReUI template is a whole product, not a screenshot. Each one ships an app shell, a full auth suite, a dashboard, profile and settings, onboarding, and the pages specific to its concept, so the first thing you do is wire up your data rather than build the tenth login form of your career.
They install with the shadcn CLI into Next.js, Vite, TanStack Start, Astro, or Laravel, and every surface is composed from the same components and blocks in the registry. That is the part that matters six months in: what you add later still matches what shipped.
On Laravel the pages are Inertia components, so they are ordinary React and TypeScript files rather than Blade with a build step bolted on. You keep Eloquent, queues and the auth scaffolding you already have, and the front end is the same registry everything else here is built from.
What is inside every template
- Every screen works. Menus, nav items, buttons, and links all resolve to real pages. No dead ends, no placeholder routes.
- One design language. A single surface mode and token set across the whole template, so it reads as one product rather than a pile of demos.
- Typed, simulated data. Swap the mock layer for your API without touching the UI. Light and dark are both designed, not auto-inverted.
- Installed the usual way. The same shadcn add workflow, pointed at the ReUI registry. The source lands in your repo with no runtime dependency on us.
- Laravel ships with Inertia. Inertia is Laravel's own way of running a React front end, so the pages are ordinary React and TypeScript components served by your routes rather than Blade with a build step bolted on. Eloquent, queues, and the auth scaffolding stay exactly where they are, and the UI is the same registry every other template here is built from.
- Your coding agent knows it too. Point Claude Code, Cursor, or any MCP client at the ReUI MCP server and it can search the registry, read a component's real API, and extend the template with the same blocks it was built from.
Components, blocks, and templates
All three come from the same registry, so moving up a tier never means switching design systems or rewriting what you already installed.
Frequently asked questions
Start building with ReUI Pro today.
Get instant access to every block, every update, and every new addition with a single license.