Airbyte Targets Fivetran's Long Tail

Diving deeper into

Conor McCarter, co-founder of Prequel, on Fivetran's existential risk

Interview
they're marketing themselves as the ETL provider for the long tail of connectors.
Analyzed 4 sources

Airbyte’s bet is that coverage can be a wedge against Fivetran’s premium reliability. Fivetran built its business by hand maintaining roughly 150 to 200 high demand connectors that data teams trust for core reporting workflows, but that leaves many smaller SaaS sources underserved. Airbyte moves connector creation and upkeep toward its community, which lets it cover more edge case apps, especially the tools used by smaller or more fragmented customers, but makes consistency and maintenance the core tradeoff.

  • In practice, long tail means the niche tools outside the core set like Salesforce, Stripe, and HubSpot. A customer may need data from a vertical SaaS app with only a few thousand users. Fivetran is less likely to prioritize that connector, while Airbyte can let the customer or community build it.
  • The business model difference is concrete. Fivetran charges for a managed connector that its team monitors and fixes when APIs change. Airbyte sells a platform and CDK for users to build or adapt connectors themselves, which expands catalog breadth but pushes more maintenance work onto users and contributors.
  • This is why Airbyte shows up as a threat without fully replacing Fivetran. Fivetran still wins where broken pipelines can corrupt revenue reporting or executive dashboards. Airbyte is strongest where having some connector is better than having none, and where engineering teams are willing to trade polish for coverage and lower cost.

The market is heading toward a split. Managed ETL leaders will keep owning the highest value, highest volume connectors, while open source and vendor built approaches absorb more of the long tail. As more SaaS companies ship native warehouse exports, the real battleground shifts from simply having connectors to owning the most trusted and cost effective data paths.