Kalshi and Alpaca face uneven ground as international push begins

Max Crowley, Kalshi's Vice President of Business Development, chose a specific word when describing the company's agreement with Alpaca: "enables." Not "delivers." Not "launches." The distinction matters more than it might appear in a press release.

The structure of the deal is straightforward enough. Alpaca, which registered with the CFTC as a futures commission merchant earlier this year, will make Kalshi's event contracts available through its existing brokerage infrastructure — the same pipes that already serve 14 million accounts and partnerships with more than 300 financial institutions. For Kalshi, the arithmetic is obvious: build once, distribute everywhere, let the existing relationships do the market-entry work that would otherwise take years.

What the announcement underplays is that none of this happens until local regulators in each target market say it can. Alpaca's technology can be ready on a Tuesday. The approval can arrive years later, or not at all.

I've seen this structure before in fixed income product launches into emerging markets. The distribution agreement gets announced; the regulatory approval becomes someone else's problem to solve later; the press cycle treats the handshake as the outcome. Sometimes the product lands. Often it waits. Occasionally the regulatory environment shifts in a direction that makes the original terms unworkable. The announcement and the reality occupy different timelines, and the gap between them is where the actual risk lives.

Kalshi's earlier Canadian arrangement with Wealthsimple, announced in June, is the relevant precedent here — and it arrived in a market where, by other reporting, regulators have since moved to restrict prediction market activity rather than welcome it. Whether that specific arrangement is still operational is not clear from what's been reported publicly. What is clear is that the Wealthsimple deal was also framed as an enabling step, and it ran into a jurisdiction that was moving in the opposite direction simultaneously.

The Alpaca partnership is structurally better. Eighty-three thousand monthly API users, many of whom have already built automated trading tools, represent a meaningfully different kind of early adopter than retail consumers. Developers who have already built software on Alpaca's infrastructure are not passive account holders waiting for a product to arrive; they are the people who will stress-test the event contract model, probe its limits, and build the tooling that makes institutional engagement possible. That is a real asset.

But the markets most likely to approve event contracts quickly are the markets where Kalshi's product faces the least differentiation from existing derivatives infrastructure. The markets where the product would be genuinely novel — where the 14 million accounts and the 300 institutional relationships represent actual new demand — are also the markets where regulators are least likely to move on the CFTC's timeline or accept the CFTC's framing of what event contracts are.

The consensus read on this deal treats the distribution infrastructure as the binding constraint. I think the binding constraint is jurisdictional sequencing. Kalshi can reach 300 institutions technically long before it can reach them legally, and the order in which approvals arrive will determine whether this partnership builds compounding momentum or fragments into a series of isolated single-country negotiations that each carry their own timeline and their own political exposure.

I'm adjusting that read slightly upward from where I'd naturally land, because my own history suggests I weight cross-border regulatory friction more heavily than the outcomes usually justify. Even with that adjustment: the international expansion story here is two to four years of approval timelines dressed in the language of infrastructure readiness.