Owning the Stack: Tribes Weigh Platform Independence in Sports Betting
Hub-and-spoke launches keep wagers on tribal servers — but the software running them still mostly belongs to someone else.
The legal architecture of tribal mobile sports betting has largely been settled by the hub-and-spoke model: bets placed anywhere in a state are routed through servers located on tribal land, so that the wager is legally deemed to occur where the sovereign sits. That framework has cleared the path for tribally controlled statewide betting in a growing number of states. But it has also surfaced a quieter question that will shape the next phase of the industry — who actually owns the technology running on those servers?
For most tribes launching sports betting, the answer today is a commercial platform provider. National sportsbook brands supply the app, the trading and risk-management engine, the payments plumbing and much of the marketing muscle, in exchange for a share of revenue and a multi-year contract. The tribe holds the license and the legal exclusivity; the operator holds the software and the customer relationship. As the market matures, some tribes are beginning to ask whether that division of labor is the right long-term arrangement for a sovereignty-based enterprise.
The case for renting the stack
There are good reasons the platform-provider model dominates. Sports-betting technology is genuinely hard: real-time odds, in-play markets, fraud and geolocation controls, and payments integration require deep engineering and constant iteration. A commercial partner brings all of that off the shelf, plus a recognized brand that lowers customer-acquisition costs and a balance sheet that absorbs the volatility of early-market losses. For a tribe entering a competitive statewide market against well-funded national books, partnering is the fastest and lowest-risk way to get live and stay competitive. Our explainer on the hub-and-spoke model lays out how the legal structure keeps the tribe at the center even when the technology is outsourced.
The model also mirrors a long-familiar pattern in Indian gaming, where management and services contracts have let tribes tap outside operational expertise while retaining ownership and regulatory control. We examine that lineage in our analysis of tribal operators and management contracts. Renting capability is not a failure of sovereignty; it is a well-worn tool for exercising it.
The strategic question is not whether outsourcing is legitimate — it plainly is — but how much of the value and the customer relationship a tribe is willing to hand to a partner over the life of a contract.
The case for owning it
The argument for building or acquiring proprietary technology comes down to margin, data and durability. A revenue-share arrangement means a meaningful slice of every wager's economics flows off-reservation to the platform provider for as long as the deal runs. Over a multi-year contract in a maturing market, that share can dwarf the up-front cost of controlling more of the stack. Owning the platform also means owning the customer data and the direct relationship — the loyalty file, the wagering history, the marketing channel — rather than accessing it through a partner whose incentives are its own.
Durability is the deeper point. A tribe that depends entirely on a single commercial partner is exposed to that partner's strategic shifts, its pricing, and its willingness to renew. Building internal capability — or acquiring technology and talent outright — converts a recurring dependency into an owned asset. For sovereigns whose entire gaming model is premised on controlling activity that occurs on their land, extending that control from the legal layer to the technology layer is a natural progression rather than a radical one.
A spectrum, not a switch
In practice, the choice is not binary. Between fully outsourced and fully in-house sits a spectrum of arrangements: white-label platforms the tribe brands and controls more tightly; joint ventures that build shared equity in the technology; consortium approaches in which multiple tribes pool resources to fund capability none could afford alone. The states now standing up tribal frameworks are where these decisions are being made in real time. Wisconsin's tribes moved forward under AB 601 with compact renegotiations still to come, and Minnesota continues to weigh a tribal-led structure — each launch an occasion to decide how much of the stack to own.
The pooling option is especially relevant to the market's structure. Individual tribes vary enormously in scale, and the same concentration that defines the casino business applies to betting technology: only the largest operators can realistically fund proprietary development alone. For everyone else, shared infrastructure across multiple tribes may be the only path to platform independence that pencils out. That is a coordination challenge as much as a technical one, but it is precisely the kind of collective capacity-building that has served tribal gaming before.
None of this suggests a stampede away from commercial partners. For most tribes, for now, the platform-provider model is the rational choice. But the direction of the conversation has shifted. As hub-and-spoke betting becomes routine and the legal questions recede, the strategic frontier is moving from the courtroom to the codebase — and the tribes that think early about how much of the stack to own will be better positioned when their first contracts come up for renewal.