The PivotNine Blog

Statsig Warehouse Native Helps Keep Data Secure

board-4855963_1920-3x2.jpg

Statsig has launched a new product called Warehouse Native that connects to your own data warehouse to analyse product experiment data, rather than sending data to an external tool.

By keeping data within the customer data warehouse, Statsig plugs into existing customer data workflows. Instead of sending telemetry data from application experiments out to a third-party tool, customers can collect data internally. The data can then be used for more than one purpose, as well as increasing the security and privacy of that data.

This aligns with a significant shift in attitude to data privacy and security among those with substantial data holdings. Government regulators are cracking down on poor practices, and new, much stricter laws governing privacy are being passed in jurisdictions worldwide.

Where organisations might have previously felt comfortable sending data between various vendor platforms with few controls, those days are ending. Customer preferences now look more like those of the pre-cloud era where organisations were hesitant to allow data to leave their corporate boundary. However, the edge of that corporate boundary now often includes cloud-based data warehouse environments. This requires a rethink of how to do data analysis.

By accessing data inside the corporate boundary, Warehouse Native can be just one of multiple analysis tools customers use to understand their data better. This can reduce data duplication, as the same kind of data can be collected once, rather than duplicated inside multiple external SaaS tools. Multiple teams can share a common view instead of working in isolated silos.

Connecting to an existing data pool also helps speed up analysis. Instead of waiting to collect a new dataset with a newly acquired tool, customers can use Statsig immediately to look at historical data they already have. Warehouse Native supports Snowflake, BigQuery, Redshift and Databricks today, with more integrations planned.

Because the source dataset is shared, analysis queries and techniques can be more easily shared between teams. This can make adoption easier, as customers can deploy Warehouse Native to one team and then grow. While the same is true of cloud-hosted Statsig, adding more teams means either working with the same dataset the original team has built, or waiting to add new datasets as each new team is added. With Warehouse Native, each additional team can use Statsig with their own existing datasets as well as sharing the datasets and analysis of the earlier teams.

Statsig Warehouse Native represents what I believe will be a very popular approach from now on. Many customers now want more control over where data lives but they still want the value of tools like Statsig. Giving customers the choice of a cloud-hosted environment as well as plugging into existing data repositories makes a lot of sense.