Managed Integration Control Towers Rise
Sara Du, co-founder and CEO of Alloy, on iPaas vs. universal APIs
The core strategic point is that integrations age like product surface area, not like one time partner launches. A marketplace gets broad coverage fast because outside developers do the initial build, but quality drops later because every API change, new field, auth update, and edge case still has to be maintained. Once integrations start breaking revenue workflows, the platform owner usually has to bring that maintenance back in house or adopt embedded iPaaS to control it centrally.
-
In practice, the hard part is not getting an app listed, it is keeping it working. Alloy describes integration work as constant data mapping, auth handling, logic updates, and release management. In the panel discussion, this ongoing work is compared to gardening, because endpoints get deprecated, fields change, and weaker partners let connectors decay.
-
App stores solve distribution, not accountability. When a user-facing integration breaks, customers rarely care which side owns it, they blame the software vendor whose product stopped syncing. That is why embedded iPaaS becomes attractive for SaaS companies, it lets product and engineering teams ship configurable integrations inside their own UI and own the support burden end to end.
-
The deeper a company goes into mid-market and enterprise, the less a loose marketplace model works. Ampersand describes how even one Salesforce integration keeps spawning tenant specific requests, custom object mappings, rate limit issues, and observability needs. That pushes the market toward infrastructure that turns one off partner code into repeatable configuration and monitored operations.
Over the next few years, the winning platforms will look less like app directories and more like managed integration control towers. AI will make first pass connector generation cheaper, but that only increases the value of owning maintenance, observability, and customer specific configuration, because those are the parts that determine whether integrations actually keep revenue flowing.