Already on my nope not even gonna try it list.

The demo page does that annoying crap where it tries to prevent you from navigating to your prior site.

I thought that trend peaked in like 2001.

I can assure you, that's a bug and not an intended feature.

Thank you for your feedback.

Nice, well done! I'm using Metabase at the moment, which I quite like, except for a few little annoyances. What was your motivation for writing this, and where do you see insights differ from the current main players like metabase, superset and redash?

Feature wise, in case you are interested, for these tools it is important to me to be able to create the graphs/dashboards in an automated way, e.g. via an api. Import/export would also be good. Also: openid support, ldap would be nice to have too, but openid would suffice.

Hey, thanks!

Regarding Metabase, Insights has full blown first class support for joins... so we don't have to write blog posts like this [1]. My research shows Metabase works great with normalised tables (like a CSV file? normalised NoSQL table, etc)... but falls short when you need to visualise relations between tables. You can look at for example all your orders, think "I wonder what's the highest grossing country" and have the results at your fingertips.

Regarding Redash, which seems to be a nice SQL editor, in Insights you don't need to know any SQL to get answers. Thus "business stakeholders" can get dirty with the data with minimal training.

Regarding Superset, I'm unfortunately not familiar with its latest features. Please somebody reply with an overview! :) Last time I checked it (many years ago), it was pretty complicated to get it installed (some python issues?) and I'm not sure if you could explore data without knowing SQL. Insights in comparison is super easy to install (npm install -g insights) and get going with.

[1]: https://www.metabase.com/blog/Joins/

I work on Metabase and wanted to say congrats on putting all this together. Excited to see more open source options for BI.

Just as a point of fact - that blog post you linked to is 3.5 years old at this point.

Even at that time we had implicit joins (for things like top grossing countries if you had an FK in your transactions back to a table w/ the country field).

We've had joins in our notebook mode for a while now (https://www.metabase.com/docs/latest/users-guide/custom-ques...)

insights is MIT-licensed and built on JS/TypeScript with a node backend. That's really appealing as a user since it means there's no need to delve into another programming language or huddle with the lawyers to figure out our legal obligations if we make changes. Contrast with the alternatives:

- Metabase is AGPL and built on clojure, making it a hard pass on both counts

- redash and superset have friendlier licenses (bsd-2 and apache-2 respectively) but are built with Python.

I totally do not get the negative comments.

Having seen a fair share of BI tools (I created and maintain an "awesome" list at [1] which I created for the sole purpose of getting an overview of what's out there) and assessing the stage you're at developing solo, you're getting quite some important UI basics very right imo.

The "Next Steps" give a great impression of what's possible and how to navigate the app.

From an E-Commerce viewpoint, most people want to flexibly play around with Products, Orders and Order Line Items and ratios between the three. Configuring this by hand in something like Google Datastudio etc. is cumbersome, even or more so in Looker (if broken out into separate Views, one needs to needs to create Merged Results Looks; if not the different cardinality objects are always connected). I feel like Insights is handling this really well. If you would add support for calculated fields, you'd offer a compelling E-Commerce controlling solution.

One issue I noticed though is that your nesting seems to be unlimited. I could open an infinite "table" tree if I start from the order_lines or product view --> order_lines --> order --> order_lines --> product --> seller --> orders/ products... ad infinitum.

You want to make sure that this drilldown into FK relationships does not lead to loops. Also I think some visual support where in the nest tree one is at (orders --> order_lines --> product --> sellers) would be great, otherwise it's quite easy to get lost.

Other than that honestly congrats on doing a lot of things right in terms of data viz, responsiveness, sharing capabilities. Really like your work!

[1]: https://github.com/thenaturalist/awesome-business-intelligen...