How Alpaca built the API brokerage for 300+ global fintechs across 45 Countries, with CEO Yoshi Yokokawa

In this episode, Lex chats with Yoshi Yokokawa, CEO of Alpaca — a brokerage infrastructure company that provides API-based trading and custody services to fintechs and developers globally.

The conversation begins with their shared experience at Lehman Brothers during the 2008 financial crisis, where Yoshi worked in fixed income securitization and learned that even when market participants sense a bubble, they keep dancing because timing the exit is impossible. After Lehman's collapse, Yoshi pursued entrepreneurship, building a computer vision AI company acquired by Kyocera before founding Alpaca in 2017. Initially inspired by Robinhood, Yoshi pivoted after experiencing firsthand the friction of accessing brokerage infrastructure—realizing the deeper opportunity was building API-first brokerage rails for developers. Today Alpaca powers 9 million accounts through 300+ partners across 45 countries, recently raising $150 million at a unicorn valuation.

The discussion explores how Alpaca follows Robinhood's product roadmap to anticipate partner demand, the challenges of adding crypto, and Yoshi's thesis that finance is undergoing a generational shift from digital to on-chain operations. Lex shares examples of legacy infrastructure dysfunction—from faxing PDFs to TD Ameritrade in 2012 to the Synapse collapse caused by manual CSV uploads—illustrating why Alpaca built its own custody and ledger systems as a path to competing in the $350 trillion global securities custody market.

NOTABLE DISCUSSION POINTS:

1. Alpaca’s biggest breakthrough was not a better investing app idea, but recognizing that the real bottleneck was brokerage infrastructure. Yokokawa and team initially explored B2C product concepts, but pivoted once they experienced firsthand how painful broker-dealer setup, custody, and clearing integrations were. For readers building fintech, this is a huge lesson: the highest-value opportunity is often the “invisible” infrastructure pain, not the user-facing feature set.
2. They found product-market fit by starting with a narrow wedge (API for automated traders) and only then expanding into a broader platform (Broker API for fintech apps). Alpaca did not begin by serving large fintechs; it first attracted power users who urgently needed programmable execution, then used inbound demand (“can I build my own Robinhood?”) as proof to build account opening, reporting, and full brokerage APIs. This is a valuable go-to-market pattern for infrastructure startups: win with a sharp use case, then expand into the system of record.
3. Yokokawa’s core strategic edge is full-stack control of licenses, memberships, and ledger technology rather than relying on legacy vendors. He explicitly ties this to lessons from historical fintech fragility (manual workflows, broken reconciliations, middleware failures) and argues that owning the custody/clearing layer is what makes Alpaca defensible long term. For readers, this is the key takeaway on moat-building in financial services: if you don’t control the ledger and operational core, your product may scale faster at first but remains structurally fragile.

TOPICS

Alpaca, Lehman Brothers, Barclays, Nomura, Neuberger Berman, Blackrock, Robinhood, Interactive Brokers, TD Ameritrade, BNY Mellon, Brokerage infrastructure, API, trading, tokenization, embedded finance, fintech, crypto, web3

ABOUT THE FINTECH BLUEPRINT

🔥Subscribe to the Fintech Blueprint newsletter to stay at the forefront of Fintech and DeFi: https://bit.ly/3hyhlC2

🤝 Partner with Fintech Blueprint through sponsorships: