Architecture template

CleenUIvs.Clean Architecture Template

The canonical Clean Architecture .NET template is a starter scaffold demonstrating layered architecture; CleenUI is a complete production codebase with 14 functional modules.

Where they fit

Jason Taylor's Clean Architecture template (20,241 GitHub stars, 255,700+ NuGet downloads) is the canonical .NET reference architecture — a layered teaching scaffold that demonstrates Domain → Application → Infrastructure → Presentation structure. It's genuine, well-regarded, and widely forked. What it doesn't include: no vertical-slice modules (you build every domain), EF Core is the only data-access option (no Dapper or stored-proc path), no RBAC, no multi-tenancy, no background services, no real-time, no React frontend — and no maintainer funding model. CleenUI is the same layered architecture, already filled with 14 functional modules, a React 18 frontend, 700+ stored procedures, and Azure Functions + WebJobs background services. One is the pattern; the other is the pattern plus 39 months of production application built on top of it.

Side by side

CategoryCleenUIClean Architecture Template
Distribution modelLicensed source code (one-time license)Open-source GitHub template (MIT)
What's in the boxLayered scaffold + 14 functional modules + 60+ React componentsLayered project scaffold (Domain / Application / Infrastructure / WebUI). EF Core only — no Dapper or stored-procedure data access option.
Architecture styleModular monolith (vertical-slice modules sitting on layered architecture)Clean Architecture (layered)
FrontendReact 18 SPA, 61 components in 12 categoriesAngular SPA in default template; community React variants exist
AuthenticationAuth0 + JWT wired end-to-end with RBAC + row-level scopingIdentity scaffolded; you wire the rest
Multi-tenancyBuilt-in (account / company hierarchy)Not included by default
Onboarding modelArchitect-led delivery availableClone the repo, follow the docs
Pricing modelCustom-scoped engagement (one-time license)Free
Adoption signalPrivate licensed deployments — customer count not published20,241 GitHub stars · 255,700+ NuGet downloads

When to pick which

Pick Clean Architecture Template

Pick the Clean Architecture template when you want to study the architectural pattern, when you're starting a small project where day-one functional scope is light, or when budget rules out a licensed codebase.

Pick CleenUI

Pick CleenUI when you want the architectural pattern AND the functional modules pre-built — i.e., when the goal is to ship a multi-tenant SaaS to production, not to study how Clean Architecture is organized.

What they share

  • Both follow layered separation-of-concerns principles
  • Both target .NET and a layered data-access approach
  • Both work as the architectural foundation for a real production application