Native Exports Threaten Fivetran
Conor McCarter, co-founder of Prequel, on Fivetran's existential risk
This risk matters because Fivetran does not fully own the sources that drive its best connector revenue. Its core product is a managed library of app to warehouse pipelines, but those pipelines sit on top of SaaS vendors' APIs, which makes the business both valuable and vulnerable. When a large source app ships its own warehouse export, customers can move the noisiest and most expensive data first, cutting into the highest usage slices of Fivetran's consumption revenue.
-
The economics are strongest where data volume is highest. Fivetran charges by usage, so connectors tied to transaction heavy apps matter disproportionately. Native exports have emerged first in categories like payments, where a vendor can package warehouse sync as an add on and capture revenue that would otherwise flow to Fivetran.
-
The product reason native wins is not just price. The SaaS vendor knows its own schema, edge cases, and roadmap better than any third party. That lets it shape the tables customers actually want, support changes faster, and turn warehouse access into a retention feature rather than sending users to another tool.
-
This does not erase Fivetran. A large part of the market is still messy, cross app, and operationally painful. Fivetran remains strong where teams want one managed tool for many common sources, and where connector reliability matters more than breadth, versus Airbyte's wider but less consistent catalog.
The next phase is a split market. Major SaaS platforms will increasingly treat warehouse sync like SSO, a feature needed to win bigger contracts, while Fivetran shifts toward being the neutral layer for the rest of the stack, especially databases, long tail apps, and monitoring across a mixed set of pipelines that no single vendor owns end to end.