Features¶
Sign-in, a user list, roles, a settings page, an audit log, a table with filters. Coworkee ships these as NuGet packages for ASP.NET Core and Blazor, and one Aspire app host starts them together.
The pages below go through it area by area, with code from the real APIs and screenshots from the demo app (catalog, documents and 100,000 sales orders).
-
Modules with
[DependsOn], a request pipeline with validation, permissions and caching, thecoworkeeCLI and Coworkee Studio. -
Users, roles, groups, permissions down to a single record, an OpenIddict auth server, Keycloak or any OpenID Connect provider, personal API keys.
-
Organisations with separated data, settings per host, organisation and user, features and editions for a SaaS product.
-
EF Core on PostgreSQL, SQL Server or SQLite, field level audit, OData with facets, a query builder and client entities that answer in the browser.
-
A MudBlazor shell with navigation, admin pages, data tables, forms generated from the model, theming and three sign-in designs.
-
Live entity changes, notifications, presence, chat, comments and ratings, mail campaigns and background jobs.
-
An assistant that works with the user's permissions, 14 model providers and an MCP server in every app.
-
Dashboards built in the browser on top of your OData sets, aggregated by the database in milliseconds.
-
23 shipped languages, texts edited at runtime and machine translation through LibreTranslate, DeepL and others.
-
One app host for database, Redis, Keycloak, Grafana with logs, metrics and traces, WebDataStudio and AspireUI.
-
A file manager with previews and public links on top of blob storage, plus full text search.
-
Back office, B2B SaaS, customer portal and Sharemee, the asset platform this framework was extracted for.
Is a framework worth it at all, compared with a plain ASP.NET Core template? Why Coworkee puts the two side by side, including where the template wins.