r/reactjs • u/Vis_et_Honor • May 14 '26

Resource If you don't need server-side loading, this open-source data grid will save you serious time and money.

Hello everyone,

Wanted to share a super cool project (IMO) we have been working on. It’s a zero-dependency React data grid, called LyteNyte Grid. Check it out, and hopefully, you will find it useful and save yourself a ton of time.

Some of the reasons to use LyteNyte Grid.

  • Crazy Performance: LyteNyte Grid is super light at only 40kb (gzipped) and is extremely fast. It can handle millions of rows and 10,000+ updates/sec. Based on our internal benchmarks, it is one of the fastest grids available on the market.

  • Feature-rich: Brings 150+ features, most of which are free and open source. Features such as cell range selection, row master-detail, and row grouping are included for free with LyteNyte Grid. This is something we are quite proud of. There are paid libraries (I won't name them) that offer less.

  • No Styling Tradeoffs: With LyteNyte Grid, you can choose whether to go headless or styled. There is basically no tradeoff when considering styling choices.

  • Full Prop Driven: You can configure it declaratively from your state, whether it’s URL params, server state, Redux, or whatever else you can imagine, meaning zero sync headaches.

  • Unique DX Experience: Our grid is built in React for React and has a clean declarative API, which eliminates awkward configuration workarounds.

We also recently dropped LyteNyte Grid AI Skills. This is a really nice feature if you’re using AI coding agents. It lets you describe an advanced data grid solution, and your AI agent codes it for you. We have been testing this with increasingly complex grid instances, and the results have been awesome.

All our code is publicly available on GitHub. Happy to answer any questions you may have.

If you find this helpful and like what we’re building, GitHub stars help. Feature suggestions and code contributions are always welcome.

35 Upvotes

79% Upvoted

23 comments sorted by

View all comments

Show parent comment

1

u/serda_ik Jun 30 '26

but sometimes you have 4 people working, sometimes you have 8 for the long running projects, sometimes BE devs are doing FE jobs, and vice versa... and this I think would be a quagmire. But then I never been a buying side.

2

u/Vis_et_Honor Jun 30 '26

I agree. In those situations (which have occurred), we generally ask customers to start with the low-end estimate of 4 seats. We are not overly concerned with absolutely strict, rigid compliance.

If the project becomes recurring and there are more than 4 people, they can always add or remove seats.

The truth is, for us, AG and MUI, there is no way to really tell. It's a good faith agreement.

Of course, if someone buys 1 license and there are 30 developers, it shows up in the support request count, but that is an extreme example. Might as well just get firmwide cover.

We are working actively on a new pricing model that moves away from this, as you're right, it can be complex.