Platform vs API for SPV Formation
Sydecar and the new atomic unit of the private markets
The split between direct SPV software and API infrastructure decides who owns the customer relationship, and who becomes the invisible rails underneath private market deals. A direct platform wins sponsors who want to launch a vehicle, collect commitments, route signatures, and handle K-1s in one place. An API model sells the same legal, banking, compliance, and ledger machinery to marketplaces, banks, and venture software that want SPVs inside their own product.
-
The platform path looks more like Shopify for emerging managers. Sydecar described customers using its app to open a deal page, invite LPs, gather signatures, receive wires, and manage post close tax and reporting. That is a branded front end business aimed at sponsors who want control of their LP experience.
-
The API path looks more like Stripe. Sydecar explicitly laid out a move from front facing software to embeddable infrastructure, so another marketplace can create entities, open bank accounts, run compliance, and track ownership on Sydecar rails without sending users to Sydecar. The Velvet integration and Monark partnership show this model in practice.
-
This is why incumbents care so much about SPV formation. AngelList built a marketplace plus back office stack, Carta bought Vauban for cross border vehicle formation, and newer players like Allocations compete by automating admin and cutting price. The winner is not just filing LLCs, it is setting the standard record for LP ownership and future transfers.
Over time, these two approaches are likely to converge, with the strongest companies running both a visible sponsor product and a hidden infrastructure layer. The strategic prize is not one time setup fees. It is becoming the system that other products trust to create vehicles, move money, maintain ownership records, and eventually support secondary liquidity inside the SPV itself.