Native exports threaten Fivetran
Conor McCarter, co-founder of Prequel, on Fivetran's existential risk
Fivetran won by turning a repetitive in house engineering chore into a shared software product. Before managed connectors, each company had engineers writing and babysitting custom scripts against the same SaaS APIs, then fixing them when schemas or rate limits changed. Fivetran centralized that work, packaged reliability as the product, and let customers buy fewer broken pipelines instead of funding their own connector maintenance.
-
The hard part was never just pulling data once. The hard part was keeping connectors working at scale. Connectors break when source APIs change, edge cases appear, or sync volumes spike. Fivetran built its brand on handling that ongoing maintenance better than internal teams could.
-
Airbyte attacked the same job from the opposite side. It used open source and community built connectors to cover the long tail faster, but that traded off against consistency. Fivetran focused on a smaller set of connectors that data teams could trust for business critical reporting.
-
That logic also explains the next wave of competition. Once large SaaS vendors saw customers paying third parties to move their data, they began shipping native warehouse exports themselves. Prequel sits inside that shift by helping vendors sell the connector directly instead of leaving the revenue and customer relationship to Fivetran.
The market is moving from horizontal connector vendors toward a mix of trusted generalists and native exports owned by the data source. Fivetran still matters wherever buyers want one service to manage many systems, but the highest value connectors increasingly get pulled back to the SaaS vendor that owns the API and the customer contract.