Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


My take is you should always just store any third-party data sources in your data warehouse, where you can then join it with all the other data. Having a feature like this just enables bad practices, and we'd rather be opinionated about how the data stack should look.

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.


Not the OP, but:

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.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: