Fivetran + dbt Labs Complete Merger to Create the Data Infrastructure for Trusted AI Agents (2026)
Snippet-only — full fetch unavailable from this environment (tier-1: HTTP 403 from the agent egress proxy; confirmed to be an organization-level egress policy denial affecting this session broadly, not a site-specific block — see evolution-log/2026-07-31/web-refresh.md for detail. Tier-4 search-snippet corroboration accepted per established KG convention for persistent-403 sources).
Key facts (corroborated across independent outlets):
- Fivetran and dbt Labs completed their merger on June 1, 2026. The all-stock transaction was originally announced October 13, 2025.
- Combined company operates initially under the name "Fivetran + dbt Labs."
- George Fraser (Fivetran) continues as CEO; Tristan Handy (dbt Labs) serves as President.
- Combined customer base described as 100,000+ data teams, including named accounts (OpenAI, Zendesk, Coupa, HubSpot) across financial services, retail, manufacturing, and healthcare.
- Same-day product announcement: dbt Core v2.0 (alpha) open-sources the dbt Fusion engine runtime under Apache 2.0.
Relevance to KG: This consolidates three layers of the composable/warehouse-native stack — ingestion (Fivetran), transformation (dbt), and reverse-ETL activation (Fivetran Activations, the former Census, acquired by Fivetran in 2025 — see source.businesswire-com.news-home-20250501266140-fivetran-acquires-census-2025) — under a single vendor. Relevant to capability.reverse-etl, vendor.census (superseded by Fivetran Activations), and the composable-CDP ecosystem-consolidation narrative already tracked via the Databricks CustomerLake and BlueConic/Blueshift acquisitions. Candidate for a vendor.fivetran body update or note in capability.reverse-etl — drafted as a candidate in today's web-refresh report for the Technical Reviewer.
Limitation: Snippet-only. No primary-source fetch confirms the dbt Fusion engine's technical scope or roadmap claims beyond what secondary press coverage states. Technical Reviewer rubric cap of 0.65 applies to any proposal grounded primarily by this source per the snippet-only fetch_status rule.