// the find
gustavnavar/Grid.Blazor
Grid component with CRUD for Blazor (client-side and server-side) and ASP.NET Core MVC
GridBlazor is a full-featured data grid component for Blazor (both WASM and server-side) and ASP.NET Core MVC, with built-in CRUD, filtering, sorting, pagination, and sub-grids. It targets teams building internal tools or admin UIs on .NET where they need a heavy-duty grid without writing one from scratch. The feature set is genuinely wide — gRPC, OData, REST, and local-data backends are all supported.
The backend flexibility is the standout feature: you can point the same component at a REST API, gRPC service, OData endpoint, or in-memory data with minimal code changes. Localization coverage is unusually thorough — 30+ language files already present, which saves real work in non-English projects. The CSS framework support (Bootstrap 3/4/5, Materialize, Bulma, MudBlazor) means it fits into whatever stack you already have rather than forcing a stylesheet conflict. The demo app is comprehensive and actually hosted, so you can evaluate behavior before writing a line of code.
The migration notes are a red flag: class names, interfaces, and package splits have changed multiple times across versions (GridCore/GridMvcCore swaps, ISGrid/SGrid type changes), meaning upgrades require manual find-and-replace across your codebase. At 732 stars it has a small community, so when you hit an edge case the documentation or a Stack Overflow answer probably won't save you. The architecture requires a compatible back-end package (GridCore or GridMvcCore) rather than working with arbitrary IQueryable sources, which creates tight coupling you'll feel during refactors. There's no mention of virtualization performance benchmarks — the virtualization support exists, but how it holds up against 100k+ rows is undocumented.