API framework

CleenUIvs.FastEndpoints

FastEndpoints is a focused ASP.NET Core API framework optimized for REPR-pattern endpoints; CleenUI is a complete full-stack codebase including the API layer.

Where they fit

FastEndpoints is a focused open-source API framework that replaces ASP.NET Core's default controller model with a REPR-style (Request, Endpoint, Response) endpoint-per-class pattern. It's a great choice for teams who want a more opinionated API library on top of ASP.NET Core. ⚠️ As of mid-2026, the FastEndpoints maintainer announced on the project homepage that the library is moving to 'bugfix-only mode' due to insufficient sponsorship — new features are paused indefinitely. Teams starting greenfield projects should factor open-source sustainability into their vendor evaluation. CleenUI is a complete full-stack codebase — the API layer is one of four tiers shipping in the box, alongside the database, the frontend, and the background services. CleenUI uses standard ASP.NET Core Web API controllers (not REPR-pattern), and has no OSS funding dependency.

Side by side

CategoryCleenUIFastEndpoints
ScopeFull-stack — API + database + frontend + background services + 15 modulesAPI library only — you build everything else
Distribution modelLicensed source code (one-time license)Open-source NuGet package (MIT)
API styleStandard ASP.NET Core Web API controllersREPR pattern (Request → Endpoint → Response)
FrontendReact 18 SPA with 61 componentsNot included — bring your own
Database layerAzure SQL + Dapper + ADO.NET + 300+ tables + 700+ stored procedures (no EF)Not included — bring your own ORM
Auth / RBACAuth0 + JWT wired end-to-end with RBAC + row-level scopingValidators + auth handlers; you wire identity
Pricing modelCustom-scoped engagementFree
OSS sustainability riskNo OSS funding dependency — licensed source code, not a framework⚠️ Announced bugfix-only mode (mid-2026) — new features paused due to low sponsorship

When to pick which

Pick FastEndpoints

Pick FastEndpoints when you specifically need a different API pattern than ASP.NET Core controllers and you're building the rest of the stack yourself.

Pick CleenUI

Pick CleenUI when you want the entire stack — not just the API layer — and you'd rather not assemble four open-source libraries plus a frontend plus a database design.

What they share

  • Both run on .NET / ASP.NET Core
  • Both prioritize developer ergonomics over framework purity
  • Both can be used together (CleenUI can adopt FastEndpoints inside an engagement)