HN Showcase
Back to browse
D8a.tech – Open-source GA4 pipeline to BigQuery, ClickHouse and more

D8a.tech – Open-source GA4 pipeline to BigQuery, ClickHouse and more

by vincentdewinter·Mar 4, 2026·2 points·0 comments
Visit ProjectView on HN

AI Analysis

●●●BangerSolve My ProblemBig BrainDark Horse

Real-time GA4 pipeline with GDPR/HIPAA compliance, not another GA4 wrapper.

Strengths
  • •Eliminates 48-hour export lag with immediate streaming and flat query-ready schemas
  • •Wire-protocol ingestion means zero frontend code changes to existing GA4 setup
  • •Solves genuine compliance pain (HIPAA PHI, data residency) that BigQuery export can't address
Weaknesses
  • •Closed beta status—unverified scale or performance claims vs established competitors like Segment/mParticle
  • •Currently free tier is limited; unclear pricing elasticity vs self-hosted ClickHouse cost
Target Audience

Data teams in healthcare, finance, and government requiring HIPAA/GDPR compliance and data sovereignty.

Similar To

Segment · mParticle · Rudderstack

Post Description

Hi HN,

I’m the founder of d8a.tech. After working in web/app analytics for 15+ years, I got frustrated with the limitations of the standard Google Analytics (GA4) BigQuery export—specifically the 24–48 hour latency and the nested schemas that make simple queries difficult.

We built d8a.tech to be a transport layer. It intercepts GA4 events and streams them directly to your own warehouse. You can self-host it.

Key technical points: - It has native drivers for BigQuery and ClickHouse for direct ingestion. - Data arrives in flat, query-ready tables. - There is no 48-hour export lag; data is available for querying (or LLM ingestion) immediately/on session end. - All enrichment happens on your infrastructure. Data never hits Google’s servers, which removes sub-processing risks for GDPR/HIPAA compliance. - It works in parallel with your existing GA4 setup. You point your current gtag or GTM container to the d8a endpoint with no frontend code changes. - It can also stream files to S3, GCS, or MinIO as a storage layer/backup.

The project is open source: https://github.com/d8a-tech/d8a

I’d love to get your feedback on the schema design and the implementation. I'll be around to answer any technical questions.

Similar Projects