A source-available Blazor UI component library with a consistent API across Bootstrap, Tailwind, Bulma, Material, AntDesign, and Fluent UI.
Blazorise is a UI component library for Blazor, a .NET web framework. It provides a set of reusable, strongly-typed components that work with multiple CSS frameworks like Bootstrap, Tailwind, and Material, allowing developers to build modern web interfaces in C# without being tied to a single design system.
.NET developers building web applications with Blazor who want a rich set of UI components with flexibility in CSS framework choice.
Developers choose Blazorise for its consistent API across different CSS providers, strong typing in C#, and the ability to switch or mix design systems without major code changes, reducing vendor lock-in.
Blazorise is a component library built on top of Blazor with support for CSS frameworks like Bootstrap, Tailwind, Bulma, AntDesign, and Material.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Blazorise supports Bootstrap, Tailwind, Material, and other CSS frameworks through provider packages, allowing UI code to remain unchanged when switching design systems, as highlighted in the README's provider-agnostic components feature.
The library offers a consistent, type-safe component API designed for .NET developers, ensuring IntelliSense support and reducing runtime errors, which is a core part of its C#-first development philosophy.
It works seamlessly with both Blazor WebAssembly and Blazor Server hosting models, demonstrated by the separate demo links for each, making it versatile for different deployment needs.
Optional subscriptions provide access to premium themes, pre-built blocks, and priority support, as detailed in the commercial licensing section, offering value for enterprise teams.
Installation requires manual steps like adding CSS/JS resources and handling query strings for cache busting, and the README references issues (#3122, #3150) with static files and PWA setup, indicating non-trivial configuration.
The dual-license model (source-available with commercial options) can be unclear for legal compliance, and premium features like themes are locked behind subscriptions, adding overhead for some teams.
Components dynamically load JavaScript resources, which might not suit projects aiming for minimal client-side scripting or those with strict performance constraints, as noted in the README's PWA considerations.