A bunch of questions.

What shortfalls in Tabix/datagrip were you trying to fix?

What’s the prime use case were you trying to improve on. What did users do before, how is that better with agx?

What do you mean by data explorer? A Table browser? Exploratory data analysis like - ydata-profiling?

How does this connect to clickhouse? Does user data go through your server?

What table library are you using?

Shortfalls in Tabix/DataGrip: While Tabix and DataGrip are powerful, they can be overly complex for quick, intuitive data exploration. AGX simplifies this by providing a more straightforward interface, making querying and visualizing data faster and easier.

Prime Use Case: AGX offers a faster, more flexible alternative to traditional tools. Before AGX, users had to deal with complex setups or configurations. AGX streamlines the experience with an intuitive interface that accelerates data exploration.

Data Explorer: AGX’s data explorer enables efficient querying and interaction with datasets, focusing on ease of use and speed. Unlike tools like YData Profiling, AGX is built for fast data exploration with quick queries and visualizations.

Connection to ClickHouse: AGX connects directly to your ClickHouse instance. No data passes through our servers—you can link your own instance, and we provide a Docker Compose setup in the repository for easy configuration.

Table Library: AGX features a custom-built table component optimized for performance and flexibility. For visualizations, we integrate Plot, enabling users to create real-time, intuitive charts from their queried data.

Initial Goal: Our initial goal was to provide a fully native experience, allowing users to query large datasets locally and access their filesystem directly. However, we expanded AGX to support remote ClickHouse instances, offering more flexibility and enabling deployment for community or customer use.

Love the use of chdb for this!