Vessel as the Vercel for Integrations
Zachary Kirby, co-founder of Vessel, on building the Vercel for integrations
The important point is that Vessel is trying to win by bundling the whole integration stack into one developer tool, not by selling a single feature. In practice, that means a product team can start with a simple unified CRM API, then add webhooks, managed ETL into its own database, cache, filtering, and app specific actions without switching vendors. That is the same core logic behind a compound startup, one infrastructure base that expands into adjacent jobs.
-
Rippling popularized compound startup as one company using shared infrastructure to launch many adjacent products, which raises wallet share and makes the suite harder to replace. The same pattern shows up in other software stacks like Brex, where one base product expands into multiple tightly linked workflows.
-
Vessel applies that pattern inside customer facing integrations. Instead of making a SaaS company buy Airbyte style ETL, a workflow tool, and a universal API separately, Vessel says the same underlying platform should handle auth, data syncing, caching, pass through actions, and custom edge cases in code.
-
That also explains the line Vessel draws against Workato and embedded iPaaS tools like Alloy. Those products grew up around internal automation or visual workflow builders, while Vessel is optimized for engineers shipping native product features, where integration depth can decide whether a deal closes.
The category is moving toward broader integration platforms, because software buyers increasingly expect deep integrations as part of the product, not as a side add on. The winners are likely to look more like compound infrastructure companies, with one core system that keeps absorbing adjacent integration jobs until buying separate tools feels unnecessary.