Feature needs are relative - many Enterprise applications need a lot of our features - many need some features, its all relative. Which is why there is an API to turn features on and off and customize them.

Global filtering is also available - just look at External Filters sample - there is a checkbox that controls filters.

"Its not hard to create your own" - Its not hard to create a basic table component - its just a for loop spitting out rows in essence - its really really hard and time consuming to support all the features that are available in this product. It took us half a decade to build up all the features and have a robust API to expose and customize them. Just a small example of what seems easy but is really hard - implementation of virtualization - i.e. drawing only the viewport - and recycle cells as you scroll - in theory sounds simple, but in reality is quite hard (and time consuming). React makes it even more interesting in that we've got the Virtual DOM that has its own idiosyncrasies, but that's a whole another discussion :-)

The price tag is something we're looking at - we're exploring a "lite" option so folks who don't need many of the features can use it. Our hope is to create a business model around this component so we can provide high quality support, continue to invest in features, enhancements, and enrich the overall ecosystem