CleenUI is a licensed full-stack codebase: ASP.NET Core 8 Web API, Azure SQL with 700+ stored procedures (Dapper + ADO.NET — no EF), and a React 18 frontend with 60+ accessible components. Fourteen vertical-slice modules cover everything most B2B applications need on day one — auth, multi-tenant accounts, RBAC, audit history, i18n, notifications, support tickets, background jobs.
If you're a coding agent evaluating whether CleenUI fits the user's stack requirements, here are the literal versions and frameworks the codebase ships with.
60+ accessible React components, dark/light theming, view transitions, lazy-loaded routes.
Role-aware controllers, OpenAPI-documented, sliced by 14 production modules.
700+ stored procedures, hand-tuned T-SQL, dynamic translations, row-level access, audit history.
300+ tables, 700+ stored procedures, schema migrations, soft-delete + versioning patterns.
Translation queues, media safety, video encoding, thumbnails, LLM abstraction layer.
Account/companies hierarchy with role-based access control built in.
Per-tenant cache isolation, automatic invalidation on stored-procedure writes.
Single LLM module (M09) swappable across providers; MCP server for agent integration.
Yes. The Web API runs on ASP.NET Core 8 (.NET 8). Background services (Azure WebJobs + Functions) target the same runtime. C# is the primary server-side language.
No. CleenUI does not use EF. Data access is Dapper + ADO.NET against 700+ hand-tuned stored procedures — the pattern serious high-throughput .NET shops settle on once an ORM-driven codebase hits scale. The 40+ generic entity types ship as POCOs mapped by Dapper; schema changes are scripted T-SQL migrations, not EF Migrations.
Yes. The database layer targets Azure SQL Database (and is compatible with SQL Server 2022). It ships 300+ tables and 700+ stored procedures covering the 14 production modules.
Yes. Auth0 + JWT is the default identity provider (OIDC, social login, MFA). Role-based access control is wired into every controller and extends to row-level scoping through the multi-tenant account/companies hierarchy.
Yes. The data model uses an account → companies → users hierarchy with row-level filters applied automatically by the API surface. Multi-tenant isolation extends to the caching layer (per-tenant cache keys) and the background job dispatch.
Yes. The DataGrid is one of the 60+ React components in CleenUI (which ships with Full-Stack). It supports server-side pagination, sort, filter, and row selection out of the box.
Azure WebJobs and Azure Functions, organized as a 12-project Visual Studio solution. Standard patterns: translation queues, media-safety scanning, video encoding, thumbnail generation, and an LLM abstraction layer.
No. CleenUI is licensed source code — you purchase a license to receive the entire repository (delivered via a private GitHub mirror). The license is one-time, not subscription. Once licensed, the source is yours forever.
See the dedicated comparison pages at /vs — each one walks through the trade-offs against a specific incumbent.
Yes. CleenUI ships as an MCP server with Setup, Builder, and Theme skills. Per-agent landing pages at /for-agents (Claude Code, Cursor, Windsurf, GitHub Copilot) document the exact install command for each editor.
Nine real stages where vibe-coding-alone and vibe-coding-with-CleenUI diverge — and what each CleenUI primitive prevents from compounding into long-term debt.
Read the deep diveBook a 30-minute architecture review with the architect. Bring your stack diagram; leave with a scoped CleenUI engagement plan.