Is it similar to https://chartbrew.com ?
Fabra is built for the modern data stack, meaning our customers already send all of their data to a central data warehouse as their single source of truth. It looks like Chartbrew connects to various third-party tools directly, which can lead to silos/discrepancies in our experience.
Fabra: Product analytics on your data warehouse
11–18 of 18 posts
Re: Fabra: Product analytics on your data warehouse
#12Earlier quoted context omitted.
Fabra is built for the modern data stack, meaning our customers already send all of their data to a central data warehouse as their single source of truth. It looks like Chartbrew connects to various third-party tools directly, which can lead to silos/discrepancies in our experience.
But allowing for integration with multiple data sources doesn't mean you can't use only one if you prefer so. Does Fabra also store the data, or only connects to an external data warehouse?
Re: Fabra: Product analytics on your data warehouse
#13How do you build a data warehouse without ETL?
We aren't a data warehouse, just the query-building and visualization layer. We let product teams easily do things like build funnels, measure trends, and more with the data they've already collected.
> Build funnels and measure trends directly on your data warehouse, without paying for costly ETL and duplicate storage in outdated analytics tools.
Not being snarky, I just don't understand. The output of an ETL is data in your data warehouse. Then you build reports on top of the DW.
How does Fabra prevent me from needing an ETL?
Re: Fabra: Product analytics on your data warehouse
#14Earlier quoted context omitted.
But allowing for integration with multiple data sources doesn't mean you can't use only one if you prefer so. Does Fabra also store the data, or only connects to an external data warehouse?
Exactly! We don't store any data and natively connect to external data warehouses. This means we're way cheaper— no need to move data or store a copy.
Re: Fabra: Product analytics on your data warehouse
#15Earlier quoted context omitted.
Exactly! We don't store any data and natively connect to external data warehouses. This means we're way cheaper— no need to move data or store a copy.
I understand, then what's the advantage compared to ChartBrew? Not having the multi-data-source feature doesn't sound like an advantage.
Since this is the "best practice" architecture, we've made the decision to focus on integrations with data warehouses specifically— Snowflake, BigQuery, etc. I don't think Chartbrew has these.
Re: Fabra: Product analytics on your data warehouse
#16Earlier quoted context omitted.
Exactly! We don't store any data and natively connect to external data warehouses. This means we're way cheaper— no need to move data or store a copy.
I understand, then what's the advantage compared to ChartBrew? Not having the multi-data-source feature doesn't sound like an advantage.
Oftentimes data teams have those data sources in the warehouse already (or a process for ETLing new ones in).
Copying data only once means lower costs (maybe) and fewer inconsistencies.
Plus if they’ve done work to join/clean/transform the data in the warehouse they can take advantage of that for product analytics without having to reinvent the wheel in ChartBrew or Mixpanel.
Re: Fabra: Product analytics on your data warehouse
#17Is it similar to https://chartbrew.com ?
Fabra is built for the modern data stack, meaning our customers already send all of their data to a central data warehouse as their single source of truth. It looks like Chartbrew connects to various third-party tools directly, which can lead to silos/discrepancies in our experience.
The only storage Chartbrew does is to cache the data while building a chart so the data source is not queried too many times and the user can see changes quicker. Afterwards, Chartbrew keeps the charts updated with data coming directly from the other tools.
Re: Fabra: Product analytics on your data warehouse
#18Earlier quoted context omitted.
We aren't a data warehouse, just the query-building and visualization layer. We let product teams easily do things like build funnels, measure trends, and more with the data they've already collected.
From your tagline: > Build funnels and measure trends directly on your data warehouse, without paying for costly ETL and duplicate storage in outdated analytics tools. Not being snarky, I just don't understand. The output of an ETL is data in your data warehouse. Then you build reports on top of the DW. How does Fabra prevent me from needing an ETL?