Application framework (.NET)

CleenUIvs.ABP Framework / ABP Commercial

ABP Commercial is a platform you build inside — compose your application from pluggable infrastructure modules using ABP's conventions. CleenUI is production modules you deploy — 14 complete vertical domain modules, 524 pre-built endpoints, and a stored-procedure-first data layer, delivered as owned source code.

Where they fit

Both ABP Framework and CleenUI eliminate the infrastructure work every SaaS team faces — auth, RBAC, audit, multi-tenancy, background jobs, real-time. The difference is the abstraction level. ABP ships a framework: a plugin model, ABP conventions, ABP Suite for code generation, and ~15 Commercial modules covering CMS, chat, forms, file management, workflows, and AI management. You compose your application inside ABP's architecture. CleenUI ships production modules: 14 complete vertical domain slices — auth, accounts, help center, translations, notifications, messaging, tasks, AI operations, assessments, marketplace — with 524 pre-built ASP.NET Core 8 endpoints and a 300+ table Azure SQL schema, delivered as owned source code with no ongoing framework subscription. The clearest single question: do you want a platform that generates your application, or a codebase that ships it?

Side by side

CategoryCleenUIABP Framework / ABP Commercial
Delivery modelOne-time licensed source code — no ongoing subscription required to keep using or deploying the codebaseOpen-core framework + ABP Commercial subscription ($2,999–$9,999/yr, 3 seats minimum)
What ships day one14 production vertical domain modules: auth, accounts, help center, translations, notifications, messaging, tasks, AI ops, assessments, marketplace, plus the full infrastructure layer~15 Commercial infrastructure modules: CMS Kit, Chat, Docs, GDPR, File Management, Forms, Payment, AI Management, Elsa Workflows, Twilio SMS, plus account/identity/audit
API surface524 pre-built, documented endpoints across 15 modules and 25 functional groupings — already written, tested, and in productionABP Suite scaffolds endpoint shells per entity — domain logic is yours to write, no pre-built domain API surface
Data accessDapper + ADO.NET — stored-procedure-first, no ORM, 700+ hand-crafted stored procedures against Azure SQLEntity Framework Core — code-first ORM, LINQ queries, migration-managed schema
How you buildYou own the source — no framework-imposed conventions; modify any file, any layer, any patternInside ABP's conventions: ABP modules, ABP services, ABP repositories, ABP UI layers — the framework shapes the architecture
FrontendReact 18 SPA — 61 accessible components in 12 categories, Storybook documentedAngular (primary), Blazor, MVC, React Native, .NET MAUI — framework-provided templates
AI capabilitiesM09 — 6-vendor LLM routing with percentage control and 3-step fallback, prompt versioning + history restore, AI agent lifecycle management, HeyGen avatar video integrationABP AI Agent with MCP support, $100–$300 AI coding credits included per tier
Vendor relationshipArchitect-led engagement — the codebase is yours perpetually after license, no renewal required to keep running or modifying itSubscription: annual renewals run $2,399–$5,999/yr; lapsed subscription means no further updates

What CleenUI ships that ABP Framework / ABP Commercial doesn't

These capabilities are pre-built in CleenUI. ABP Framework / ABP Commercial has no equivalent — you'd build them from scratch or wire a third-party integration.

Stored-procedure-first data layer

700+ hand-crafted Azure SQL stored procedures via Dapper + ADO.NET, no Entity Framework. ABP's primary data access is EF Core with ORM-managed migrations. The stored-procedure pattern gives data teams explicit query control, auditable execution plans, and zero ORM abstraction overhead.

14 vertical domain modules

M01–M15 covering accounts, help center articles + search, translation management, notification template engine, SignalR messaging, task management, AI model operations, font management, legal policy versioning, taxonomy, assessment instruments, and vendor marketplace. ABP Commercial ships ~15 infrastructure modules (CMS, forms, workflows, file management, Twilio) — platform plumbing, not vertical domain logic.

524 pre-built API endpoints

A real, documented, production-tested API surface — 524 endpoints across 15 modules. ABP Suite generates endpoint scaffolding on demand; the surface count is however many endpoints you've generated and filled with domain logic.

One-time license, no renewals

CleenUI is a per-engagement one-time license. The codebase is yours forever — no renewal required to keep running, modifying, or deploying it. ABP Commercial is an annual subscription; lapsed subscriptions mean no further updates.

When to pick which

Pick ABP Framework / ABP Commercial

Pick ABP Commercial when you want an established framework with a community, rich documentation, and a plugin ecosystem. Also reach for it when Angular or Blazor is your preferred frontend, when Entity Framework Core is required, when the framework-convention model (ABP DDD layers, ABP services) fits your team's architecture preferences, or when ABP's infrastructure modules (CMS, workflows, forms, AI Management) match your product needs more closely than CleenUI's vertical domain modules.

Pick CleenUI

Pick CleenUI when you want to deploy domain modules that are already built — not scaffold them. ABP Commercial ships ~15 infrastructure modules; CleenUI ships 14 vertical domain modules. That's the clearest single differentiator. Also pick CleenUI when a stored-procedure-first data layer is required (no EF, 700+ named stored procs), when React 18 is the frontend, when you want to own the source with no ongoing subscription, or when architect-led delivery is the right model for your team's start.

What they share

  • Both target ASP.NET Core as the backend runtime
  • Both ship multi-tenancy with role-based and claim-based access control
  • Both include audit logging, soft-delete patterns, and real-time notifications
  • Both follow modular monolith architecture — one deployable, multiple logical modules
  • Both include MCP server integration for AI-agent development workflows