I'm a co-founder of Dataland.io where we're building a powerful dataset viewer + search engine that can work on top of your Postgres or data warehouse.
We designed it specifically to provide an excellent UX to business users while reducing BI burden on the data team. We find that most business users often just need to search, filter, and sort instead of looking at charts to make operational decisions.
UX-wise, what sets us apart are:
- <1s full-text search (even on billions of rows of data), feels like Cmd+F in Google sheets, but faster
- Performance: we stream billions of rows into the web browser, seamless scrolling (no paging of 50 records at a tieme)
- Rich cells make tables easier to scan/read (enum strings => colored tags, numbers => color-coded based on value => checkboxes, timestamptz => clear date time pills)
If that fits what you need, happy to give you a demo.
arthur(at)dataland.io
Otherwise, I think the simplest BI (if charts are impt) could be something like evidence.dev or Metabase.
But I also think it's going to require some curation on your part. Can you reasonably expect business users to navigate the entire schema/table tree across these three sources? That's where I think the bottleneck often lies -- if your BI tool allows engineering to just expose a subset of curated core tables.
We designed it specifically to provide an excellent UX to business users while reducing BI burden on the data team. We find that most business users often just need to search, filter, and sort instead of looking at charts to make operational decisions.
UX-wise, what sets us apart are:
- <1s full-text search (even on billions of rows of data), feels like Cmd+F in Google sheets, but faster
- Performance: we stream billions of rows into the web browser, seamless scrolling (no paging of 50 records at a tieme)
- Rich cells make tables easier to scan/read (enum strings => colored tags, numbers => color-coded based on value => checkboxes, timestamptz => clear date time pills)
If that fits what you need, happy to give you a demo.
arthur(at)dataland.io
Otherwise, I think the simplest BI (if charts are impt) could be something like evidence.dev or Metabase.
But I also think it's going to require some curation on your part. Can you reasonably expect business users to navigate the entire schema/table tree across these three sources? That's where I think the bottleneck often lies -- if your BI tool allows engineering to just expose a subset of curated core tables.