Universal APIs Cover Only 20-30%
Sara Du, co-founder and CEO of Alloy, on iPaas vs. universal APIs
The real limit of a universal API is that it standardizes the easy middle of an integration, not the messy edges where software actually becomes usable in production. It can usually fetch and write common fields across five systems fast, but it often stops short of custom fields, tenant specific logic, user facing setup, error handling, and the ongoing maintenance needed when each customer has a different Salesforce or NetSuite setup.
-
Universal APIs are strongest when a product only needs a common schema, like employee directory data, payroll deductions, or basic ticket objects. That works well for analytics, onboarding, and lightweight sync. It breaks down when customers want their own objects, mappings, permissions, and workflow rules.
-
Embedded iPaaS and deeper native integration tools exist to handle the remaining work. They let a SaaS company expose configuration inside its own product, so a customer can choose fields, map records, set triggers, and manage exceptions without waiting for engineering to hard code another one off integration.
-
The competitive line in integrations is shifting from who can connect fastest to who can support the most demanding customer environments. In HR and payroll, a shared model can go far. In ERP and CRM, enterprise customers customize so heavily that depth, observability, and per tenant control matter more than a single schema.
Over time, basic connector work will get cheaper and more automated, which makes the uncovered 70 to 80% even more important. The winners will be the platforms that turn integration from a one time API connection into a full product capability, with configuration, monitoring, and enterprise grade depth built in.