[ancieque]

We have looked into metabase ourselves initially as well but found it lacking compared to Superset. What are your thoughts on that?

Note that we build dashboards for customers that end up having some complex SQL directly in Superset.

[lawrjone]

We do very similar things ourselves: our insights product (https://incident.io/learn) uses Metabase to power the dashboards.

The data that goes into those insights can be quite complex and the queries are actually threading JSON parameters through into BigQuery SQL queries using JavaScript UDFs to power the filters in the dashboard (show incidents with these custom field values). This works pretty well with signed Metabase dashboard links.

We have hit limitations with Metabase though. Performance of the instance can be a bit unpredictable and their support has been poor when things do go wrong, with very little willingness to take our feedback into account for new product features.

For that reason and more (such as more flexible dashboards) we’re going to move ourselves to Omni (https://omni.co/) for internal business analytics use cases, and will reconsider Metabase for our customer facing product dashboards when we do. Omni may work for these or we might build them bespoke, we’ll see at the time.

[Cyphase]

Do you have any thoughts on Superset? Did you consider it as a candidate?

For anyone who doesn't know: https://superset.apache.org/

(There's at least one service that offers managed Superset hosting if that's what you're looking for; it's easy to find so I won't link it here.)

[ancieque]

Curious, have you tried speeding things up with e.g. cube.js? We used it in a fully custom project and it was a Performance life saver. It works quite well with Superset actually.