// the take
A dotnet-new template package that scaffolds a Blazor app with MudBlazor already wired in, covering both the Blazor Web App model (Server/WebAssembly/Auto interactivity) and a standalone WASM app, with optional Individual/B2C/SingleOrg auth. It's for .NET developers who want to skip the boilerplate of registering MudBlazor services, importing its CSS/JS, and setting up Identity by hand.
Mirrors Microsoft's own webapp template flags (-int, -au, -ai) almost one-to-one, so anyone who's used dotnet new webapp already knows the surface area. It's maintained by the MudBlazor team itself rather than a third party guessing at the correct wiring, and it's already tracking the .NET 10 Web App template as its base. Real CI (mudblazor-ci, release, autotriage workflows) and localized template strings for a dozen languages suggest this gets actual maintenance, not a one-off dump.
It's a one-time scaffold, not a dependency — once generated, the Identity/auth boilerplate and MudBlazor theme choices are frozen in your project; dotnet new update only refreshes the template package, it does nothing for projects you already created. The interactivity x auth x empty x local-db parameter matrix is large and clearly not fully smoothed over — the README itself admits the WASM + Individual auth combo hits a MissingAuthority warning by default. Beyond the stock Counter/Weather demo pages there's no real layout pattern (nav shell, tables, dashboard) baked in, so you're getting a MudBlazor-flavored version of the default template, not an opinionated starter for a real app.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →