[fifilura]

My limited experience with Tableau is that it felt like Excel on speed. And heavily burdened by legacy (just like Excel or any Microsoft product is by the way).

While what we wanted was something that was SQL-native.

Back in the days we opted for a tool called Chartio which was later engulfed by Atlassian/Jira. Not sure what happened to it after, but it suited our purpose fine enough. Just line-charts and easily editable SQL.

I have some experience with Superset, but it was not really built for customer facing dashboards. Mainly useful for internal use.

Blazer as someone else posted sounds interesting. May check it out.

[hughess]

You might be interested in Evidence, a SQL-based open source BI tool where all content is version-controllable. Disclaimer: I’m one of the maintainers. A lot of companies use Evidence for customer facing and embedded reporting.

https://github.com/evidence-dev/evidence

Previous HN discussions:

https://news.ycombinator.com/item?id=35645464 (97 comments)

https://news.ycombinator.com/item?id=28304781 (91 comments)

[Temporary_31337]

What’s different between an internal dashboard and a customer facing one? I am mostly asking what specifically is missing from Apache Superset as we are seriously looking into it… for internal use

[fifilura]

I have some recollection about filters defined by jinja macros opening up for SQL injections.

[fifilura]

And this would be fine if you could lock down arbitrary input in e.g. dropdowns, but it was still possible to input arbitrary strings even in a dropdown because of the choice of widget.