Google Cloud is teaming up with SQD to bring blockchain data analytics into BigQuery. The collaboration means developers and data analysts will be able to run SQL queries against indexed on-chain data without pulling it out of Google's data warehouse. It's a move that treats crypto data like any other dataset.
How the integration works
SQD maintains indexed blockchain data across several networks. Under this partnership, that data will be exposed inside BigQuery as a native source. For users, that means they can join on-chain activity with existing tables and run standard queries. A question like "how many unique addresses interacted with this contract last week?" becomes a simple SQL statement. No need to build a custom indexing pipeline or move data around.
Who the audience is
The setup is aimed at data teams who've avoided blockchain work because of the heavy upfront infrastructure. Instead of standing up nodes and managing indexes, they'll rely on SQD's data and Google Cloud's backend. It's also useful for businesses that need to track on-chain behavior for compliance or customer insight. The barrier to entry drops considerably.
What's still unclear
Neither company has said which blockchains will be covered first, nor how often the data will refresh. There's no timeline for general availability or pricing details. The announcement reads more like a directional statement than a product launch. Those specifics will have to come later.
This is a signal that blockchain data is becoming a standard part of the cloud stack. Rather than forcing developers to use separate tools, BigQuery is turning on-chain information into just another table. That makes it easier for crypto teams to work with the same infrastructure their non-crypto colleagues use, and it pushes the wider industry toward a future where on-chain analytics is mundane.
The integration is still in early stages. Google Cloud and SQD haven't said when it'll go live, but the direction is clear: blockchain data is moving into the same data warehouses that handle everything else. That shift isn't going to be undone.
