Project template

CleenUIvs.ASP.NET Core + React Template

Microsoft's dotnet new template scaffolds an empty ASP.NET Core + React project; CleenUI ships a complete production codebase on the same stack.

Where they fit

Microsoft's official 'dotnet new react' template scaffolds an empty ASP.NET Core + React project — minimal API, default Vite frontend, identity scaffolded but not wired. It's a starting point. CleenUI is the same stack but with the entire application built out: 14 functional modules, 524 documented endpoints, 60+ accessible React components, 300+ database tables, end-to-end auth + RBAC + audit + i18n + notifications + background jobs. Think of it as 'dotnet new react, three years later, after a senior architect has spent that time on the foundation.'

Side by side

CategoryCleenUIASP.NET Core + React Template
What you get day oneComplete production codebase with 15 modulesEmpty scaffold with sample weather endpoint
Distribution modelLicensed source code (one-time license)Free template from Microsoft
Tech stack.NET 8 + React 18 + Dapper/ADO.NET (no EF) + Azure SQL + Auth0.NET 8 + React (Vite)
Frontend61 accessible components in 12 categoriesDefault Vite + React; no UI library
AuthenticationAuth0 + JWT + RBAC + row-level scopingIdentity scaffolded; you wire the rest
Modules included14 vertical-slice modulesNone
Database schema300+ tables, 700+ stored proceduresNone — you design it
DocumentationStorybook + Postman/OpenAPI + per-module deep-dive pages + Codebase tourMS Learn docs
Pricing modelCustom-scoped engagementFree

When to pick which

Pick ASP.NET Core + React Template

Pick the dotnet new template when you're starting a small, isolated project where 'just enough scaffolding' beats 'opinionated foundation,' or when budget rules out a licensed codebase.

Pick CleenUI

Pick CleenUI when you're building a multi-tenant B2B SaaS — the 6-12 month gap between 'empty scaffold' and 'shippable foundation' is the actual product you're paying for.

What they share

  • Both target .NET 8 + React 18
  • Both use Vite for the frontend build
  • Both can host an OpenAPI / Swagger spec