ReportsHQ compared with Metabase
Metabase queries the database you already have, which is more powerful and needs someone who writes SQL. This reports on a stream of events with no query to write.
Metabase queries the database you already have
That is a real advantage. Your production data is already there, already correct, already joined, and nothing new has to be sent anywhere. If your team has somebody who writes SQL comfortably, Metabase will answer questions this product cannot express at all.
This reports on a stream of events
There is no query to write and no schema to understand, because the shape is fixed: events with a name, a value and some properties. That constraint is what lets a report create itself the first time an order event arrives, and it is also the ceiling on what you can ask.
Where Metabase wins
Anything needing a join, a window function, or a question nobody anticipated. Reporting on state rather than events, such as how many subscriptions are active right now, which is a query against your tables and not something a stream of events answers well.
Where this wins
Time to the first correct report, sharing with people who will never have database access, and not pointing a reporting tool at your production database in the first place.
If nobody on the team writes SQL
That is the case this is built for. If somebody does, and they enjoy it, Metabase is probably the better answer.
Start free