Our Vision
Give Blazor teams an elegant UI foundation that can become fully their own.
Blazorise starts with proven design systems and CSS frameworks, but the goal is broader: provide the components, utilities, customization model, and developer experience needed to build rich applications that match your product, your brand, and your users.
100+
UI components
A broad component foundation for application UI, workflows, and product features.
7+
CSS providers
Provider flexibility without forcing teams into one visual system.
1 API
Consistent model
A predictable Blazor component model across providers, themes, and app types.
Beyond implementing a CSS framework
Framework guidelines are an excellent starting point, but applications need more than guidelines. Real products need data workflows, validation, dashboards, navigation, responsive layouts, theming, localization, and components that are simply not covered by a single design system.
Blazorise is built to be a general-purpose Blazor UI library. It should feel natural with Bootstrap, Tailwind, Fluent 2, Bulma, Material, Ant Design, and future providers, while still giving teams room to express their own brand.
We do not want every Blazorise application to look the same.
The best outcome is when companies succeed with Blazorise in a way that feels unmistakably like their own product: close to a provider's visual language when useful, and fully customized when the business needs it.
What we are building toward
Blazorise should provide the low-level and high-level tools needed to build rich user interfaces with Blazor.
Composable components
Deliver encapsulated components that can be combined into complex product workflows.
Deep customization
Make themes, providers, utilities, and component parameters flexible enough to match real brands.
Provider independence
Let teams choose the visual foundation that fits their project without changing how they think about UI.
Accessible by default
Keep accessibility and cross-browser behavior part of the foundation, not an afterthought.
Developer joy
Keep APIs understandable, discoverable, and productive for both new and experienced Blazor developers.
Community learning
Build an environment where customers, contributors, and maintainers learn from one another.
From a developer's point of view
The library should make everyday UI work calmer and more predictable. Teams should be able to compose components, customize them deeply, and learn from examples without fighting the framework.
Components should own their behavior while remaining easy to compose and extend.
Teams should be able to adapt Blazorise to their product identity instead of adapting their identity to Blazorise.
Application UI should work across browsers, devices, input modes, and user needs.
The project should promote useful feedback, practical examples, and shared learning.
A UI library that grows with real applications
Blazorise will keep expanding where product teams need practical building blocks: deeper components, stronger customization, better utilities, accessible patterns, and documentation that helps new and experienced developers move together.