iPaaS Outlasts Universal API Hype
Sara Du, co-founder and CEO of Alloy, on iPaas vs. universal APIs
The durable opportunity is not the number of new universal API startups, it is the shift in buyer behavior from building integrations in house to buying infrastructure. The fundraising wave made the category look crowded, but the real driver is that every SaaS product now needs more integrations, and teams have learned that maintaining dozens of connectors, auth flows, and schema changes is a permanent tax on engineering.
-
Universal APIs win the initial sale because they let a company stand up light read and write integrations quickly, but they usually cover only the common fields and workflows. As customers ask for custom fields, ERP logic, or user level configuration, products often need a deeper embedded iPaaS or native integration layer on top.
-
The boom also reflects fragmentation. Finch described HR and payroll as so fragmented that reaching roughly 75% market coverage can require 40 to 50 connectors. That kind of mess creates room for specialists like Finch in employment, Rutter in commerce, and broader platforms like Alloy that try to reuse the same engine across categories.
-
What shakes out is less about who has a unified schema and more about who owns the hard parts, partner access, monitoring, data extraction, and higher level products. Across the category, founders converge on the same point, pure connector layers get cheaper over time, so the lasting businesses add workflow, payments, analytics, or other value added services on top.
From here, the market should consolidate around a smaller set of platforms with either deep vertical authority or a broader workflow product that goes beyond simple data pipes. As AI makes connector creation faster, advantage shifts even more toward partner relationships, proprietary data, and product layers that turn raw connectivity into a business outcome.