Key Takeaways
- Combined monthly volume on Kalshi and Polymarket rose from under $5 billion in September 2025 to roughly $53 billion in July 2026, sustaining above $45 billion in August after World Cup trading ended.
- Robinhood’s event contracts division generated $156 million in Q2 2026 revenue on 13.6 billion contracts, overtaking its crypto trading revenue less than 18 months post-launch.
- The CFTC’s proposed framework (June 2026) permits broad sports outcome contracts settled on league-verified data, while prohibiting contracts on injuries, officiating calls, and discrete in-game actions.
- High-profile disputed settlements—such as Polymarket’s $60 million Bitcoin dispute and $7 million Ukraine mineral deal—highlight that deterministic oracle and resolution design is what separates a solvent venue from a contested one.
- Custom in-house prediction market platform development costs between $80,000 and $500,000+ across 6 to 19 months—excluding U.S. exchange registrations (DCM) that can exceed two years—compared to white label turnkey deployments delivered in weeks.
Event contracts have moved from a niche crypto experiment to a mainstream financial asset class in under two years. Trading volume that historically clustered around U.S. presidential cycles now spans sports, monetary policy, corporate milestones, commodities, and macroeconomic indicators—persisting between headline events rather than collapsing in off-cycles.
Robinhood illustrates the velocity of this financial shift. After launching its prediction markets hub in March 2025, the brokerage generated $156 million in quarterly revenue from the product by Q2 2026, overtaking its crypto transaction revenue. Traditional brokerages, sportsbooks, and consumer fintech platforms are arriving at the same realization: their existing user base already maintains funded balances and exhibits strong demand for short-duration event derivatives.
Closing the gap between market demand and running an active trading venue presents structural engineering challenges. A prediction market is an exchange paired with a deterministic settlement mechanism: it requires central limit order book (CLOB) matching, collateral management, market lifecycle administration, tamper-resistant dispute resolution, and jurisdiction-specific compliance modules. White label prediction market software supplies this core transactional engine, allowing operators to focus on distribution, brand equity, and liquidity.
Why Prediction Market Trading Volume Keeps Rising
Demand for event contracts has decoupled from isolated political cycles. Monthly trading volume across decentralized and centralized venues grew from $1.2 billion in early 2025 to more than $20 billion by January 2026. Combined volume on Kalshi and Polymarket reached roughly $53 billion in July 2026 on the back of World Cup trading. August 2026 volume normalized to $45.3 billion post-tournament—retaining a 77% gain over May 2026 volume ($25.7 billion).
Participation is broadening as well as deepening. Unique active wallets tripled to 840,000 in the six months leading into February 2026, which indicates new traders arriving rather than a small group simply increasing position sizes.
Distribution is the other driver. DraftKings and FanDuel both launched prediction products in December 2025, and Robinhood, Fanatics, and Coinbase now offer event contracts inside apps their users already trade or bet on. Prediction markets are becoming a feature of platforms with millions of funded accounts rather than a standalone destination.
Institutional Capital and Regulatory Clarity: Why Operators are Launching Now
Beyond demand, two shifts made the category viable for new entrants.
Regulatory direction clarified. U.S. courts cleared election contracts in October 2024, and the CFTC published a proposed framework for event contracts in June 2026. The direction of travel is toward a defined perimeter rather than an open question, which is what institutional capital and licensed operators need before committing.
Capital validated the model. Intercontinental Exchange committed up to $2 billion to Polymarket at an $8 billion valuation in October 2025. Both leading venues carried valuations above $20 billion during 2026. Distribution platforms followed with their own capital: a joint venture between Robinhood and Susquehanna acquired MIAXdx in January 2026 and launched Rothera, a CFTC-licensed exchange and clearinghouse, in June 2026.
Category mix also shows where demand actually sits. Between July 2024 and April 2026, sports accounted for roughly 80% of Kalshi’s volume, while Polymarket’s international book split closer to 39% sports, 32% politics, and 20% crypto. Operators planning a launch around political cycles are aiming at the smaller share of the market.
Prediction Market Mechanics: How Binary Outcome Contracts Settle
A prediction market is an exchange where participants buy and sell contracts tracking the outcome of specific real-world events.
Each share trades at a price between $0.00 and $1.00, and that price reflects the market’s implied probability of the outcome. When the event resolves, winning shares pay out at $1.00 and losing shares expire worthless. Traders can also sell positions before resolution, locking in gains or cutting losses as new information arrives. The underlying mechanics are covered in more detail in how crypto prediction markets work.
What a White Label Prediction Market Platform Is
A white label prediction market platform is pre-built, turnkey exchange infrastructure that allows businesses to launch a proprietary, branded event contracts venue without building the underlying trading engine.
The software vendor supplies the order-matching engine, automated settlement logic, oracle connectivity, smart contract architecture (for hybrid/decentralized setups), and administrative tooling. The operating firm retains control over user acquisition, front-end visual identity, domain management, fee structures, customer support, and local licensing compliance.
Unlike a spot exchange that settles against continuous asset price feeds, a prediction market must systematically verify binary or multi-outcome states from external real-world events—requiring deterministic, dispute-resistant resolution architecture.
Core Components of a Turnkey Prediction Market Stack
An enterprise-grade white label deployment integrates six distinct functional layers:
| Layer | What it does | What to confirm before signing |
|---|---|---|
| Matching and pricing engine | Executes trades, maintains the order book, enforces position limits | Throughput under peak load, latency benchmarks, order types supported |
| Market lifecycle tooling | Creates markets, defines resolution criteria, schedules open and close times, handles cancellations | Whether operators can create markets independently or must file requests with the vendor |
| Collateral and settlement | Holds trader collateral, locks it against open positions, executes payouts at resolution | Settlement speed after resolution, segregation of operator and trader funds |
| Resolution and oracle layer | Determines the outcome and handles disputes | Data sources, dispute path, who holds final authority |
| Compliance controls | KYC, transaction monitoring, geo-fencing, audit trails, reporting | Which controls are native versus third-party integrations the operator must contract separately |
| Front end and admin console | Trader-facing web and mobile interfaces, operator dashboard for positions, volume, and settlement oversight | Depth of white labeling, whether mobile is included, API access for custom front ends |
Two items sit outside almost every white label package and belong in the operator’s budget from day one: legal authorization in each target jurisdiction, and user acquisition. Vendors supply infrastructure, not licenses and not traders.
Order Book Architecture vs. Automated Market Makers (AMMs)
Institutional liquidity requires performant matching infrastructure. While early decentralized protocols relied on Automated Market Makers (AMMs), modern high-volume prediction exchanges rely on Central Limit Order Books (CLOB).
| Order book feature | Why it matters for event contracts |
|---|---|
| Continuous bid and ask from participants | Prices update in real time as participants react to news, not through a formula that lags. |
| Spreads tighten as makers compete | Traders pay less to enter and exit positions |
| Resting depth absorbs large orders | Size trades without moving the price sharply |
| Supports institutional and algorithmic makers | The venue can host the professional flow that supplies most liquidity |
| Price-time priority matching | Fair, auditable execution that holds up under regulatory review |
Spread discipline matters more here than in most asset classes. Event contracts trade on narrow probability increments, and a one-cent spread on a $0.50 contract is already a 2% cost to the trader. Every cent of additional spread pushes away the high-frequency participants who supply most of the resting liquidity.
Data from early 2026 shows mid-frequency traders and high-frequency market makers together accounted for the overwhelming majority of activity, while single-trade participants represented less than 0.2%. A venue built to host professional flow is competing for the largest segment of the market.
Depth on day one comes from planning. Operators secure it through designated market maker agreements, internal seeding, or liquidity aggregation from external venues, and infrastructure with built-in liquidity frameworks shortens the path to tradable depth. The plan for the first ninety days should be settled before launch.
How Prediction Market Operators Generate Revenue
Revenue in event markets comes from four sources, and their mix determines how much volume a venue needs to be viable.
- Trading fees or spread. A percentage of notional volume, a flat per-contract fee, or a share of winnings. This is the primary line for nearly every venue.
- Settlement fees. A charge applied at payout, often on the winning side only.
- Market creation fees. Charged when third parties list their own markets on the venue.
- Ancillary revenue. Data licensing, premium analytics, and API tiers for algorithmic participants.
Small per-contract fees compound quickly at scale. Robinhood caps its prediction market fee at $0.01 per contract, yet 13.6 billion contracts traded in Q2 2026 turned the product into a $156 million quarterly revenue line.
The arithmetic is unforgiving at low volume and attractive at scale. A venue running $500,000 in daily volume at a 2% effective take generates roughly $10,000 per day in gross revenue, against which sit infrastructure fees, market maker incentives, compliance costs, and acquisition spend. Most operators reach viability through an existing user base rather than cold acquisition, which is why the strongest launches have come from platforms that already hold funded accounts.
What Regulatory Compliance Looks Like Under CFTC Event Contract Rules
Event contracts sit in different legal categories depending on where the trader is located, and the compliance perimeter is an operator obligation that no vendor can assume.
In the United States, event contracts fall under the Commodity Futures Trading Commission (CFTC) as derivatives rather than under state gaming regulators. The proposed framework published in June 2026 revises the rule governing contracts deemed contrary to the public interest. Its structure is a permitted list and a prohibited list.
| Generally permitted | Generally prohibited |
|---|---|
| Broad sports outcomes settled on league-verified data, including final scores, tournament advancement, and season statistics | Contracts creating incentives around player injuries |
| Economic indicators such as CPI, GDP, and unemployment | Contracts on officiating decisions |
| Financial indicators and foreign exchange rates | Discrete in-game action contracts |
| Election outcomes | Physical altercation contracts |
| Award contests | Pre-collegiate sports contracts |
| Terrorism, assassination, and war contracts |
Listing runs through self-certification, with a 90-day window for the Commission to determine that a contract is contrary to the public interest. The comment period on the proposal closed in July 2026, and the final text can differ from the proposal, so operators building U.S.-facing catalogs should treat the boundaries as directional rather than settled.
Outside the United States, treatment varies widely. Some jurisdictions regulate event contracts as gambling products requiring a gaming license, others as financial instruments under a markets framework, and several prohibit them outright.
Practical consequences for the build are concrete: geo-fencing enforced at account and transaction level, market catalogs filtered per jurisdiction so a trader in one market never sees a contract type they cannot legally trade, Know-Your-Customer (KYC) tiering that matches the strictest applicable rule, transaction monitoring against sanctions and illicit finance typologies, and audit trails detailed enough to reconstruct any settlement on request.
Compliance-ready infrastructure means these controls are built into the software and configurable per jurisdiction. It does not substitute for legal authorization, and any operator plan that treats licensing as a post-launch task has the sequence backward.
How Much Does It Cost to Build a Prediction Market In-House?
Building in-house means paying for two separate projects: the exchange software and the compliance program around it. Published estimates put the software alone at roughly $80,000 for a minimal build to $500,000 or more for an enterprise-grade platform, delivered over six to nineteen months.
| Cost line | Published in-house estimate | Covered by a white label platform? |
|---|---|---|
| Core platform (matching engine, settlement, admin, front end) | $150,000 to $500,000+, over 9 to 19 months | Yes, deployed in weeks |
| Native iOS and Android apps | $30,000 to $80,000 | Confirm scope with the vendor |
| Oracle and data feed integration | $5,000 to $20,000 | Yes |
| Payment infrastructure | $10,000 to $30,000 | Integrates with the operator’s existing rails |
| Smart contract audits (on-chain settlement only) | $25,000 to $150,000 | Confirm scope with the vendor |
| Ongoing maintenance | $30,000 to $100,000 per year | Yes, under the vendor agreement |
| KYC and AML tooling | $5,000 to $20,000 setup, plus $0.75 to $5.00 per verified user | Controls built in; per-user verification fees remain |
| Legal and licensing | $50,000+ in U.S. legal fees, before any registration | No, always an operator cost |
Compliance is where in-house timelines stretch furthest. A U.S. venue needs a CFTC designation as a Designated Contract Market (DCM), and while the statutory review period is 180 days, it only starts once the application is deemed materially complete. Recent applications have run well beyond two years. Applicants must also show capital covering more than twelve months of operating expenses and have a chief regulatory officer, market surveillance lead, and investigations staff in place at the time of filing.
The alternative to applying is acquiring. Polymarket paid $112 million for QCEX, a CFTC-licensed exchange and clearinghouse, in July 2025 to regain a legal path to U.S. users. Outside the United States, gaming or financial licenses carry their own application fees, capital requirements, and local counsel costs per jurisdiction.
A white label platform removes the software build and most of the engineering behind compliance controls from the budget. Legal authorization and the compliance team that operates those controls stay with the operator either way. These are published ranges and should be treated as directional inputs to a budget, not quotes.
What Operators Handle When Launching With a White Label Vendor
A white label vendor delivers and maintains the platform. The parts that decide whether the venue succeeds sit on the operator’s side of the agreement.
| Area | Vendor supplies | Operator handles |
|---|---|---|
| Legal perimeter | Configurable geo-fencing and jurisdiction filters | Licensing, legal review, and target market selection |
| Market catalog | Market creation and lifecycle tooling | Category selection, contract wording, and settlement sources |
| Liquidity | Order book and liquidity frameworks | Market maker agreements, seeding, and incentive budget |
| Integration | APIs and integration surface | Connecting identity, balances, payments, and banking |
| Brand and growth | White label front end | Brand, UX decisions, and user acquisition |
| Operations | Admin console and monitoring tools | Customer support, dispute handling, and compliance staffing |
- Licensing and the jurisdictional perimeter. Decide which markets the venue will serve, confirm the legal treatment of event contracts in each, and begin any licensing process before technical scoping. The market catalog, KYC design, and geo-fencing rules all depend on this answer.
- Market catalog and resolution sources. Select categories that match the licensed perimeter and audience, write resolution criteria in unambiguous language, and name a settlement source for each category. Objective, verifiable sources reduce dispute exposure more than any other single decision.
- Liquidity commitments. Sign designated market maker agreements, set the incentive budget, and decide how much internal seeding the venue will run in its first ninety days. The vendor supplies the order book; the operator supplies the reasons for makers to quote on it.
- Integration with existing systems. Connect the platform to existing identity, balance, and payment systems, and settle banking relationships for deposits and withdrawals. Operators with an existing user base should prioritize a single account and single funded balance across products.
- Configuration and launch sign-off. Set fee schedules, position limits, and jurisdictional filters, then sign off on load tests at multiples of expected peak, settlement rehearsals that include at least one deliberately ambiguous outcome, and geo-fencing checks under Virtual Private Network (VPN) conditions.
- Operations and growth after launch. Staff customer support and compliance review for event peaks, own the dispute escalation process, and fund user acquisition. Open with a small set of high-liquidity markets in one or two categories, then expand as depth builds.
How to Evaluate a White Label Provider
Vendor differentiation in this category is mostly asserted rather than demonstrated, and the claims that matter are the ones that can be tested before signing.
| Evaluation area | Question to put to the vendor | What a weak answer looks like |
|---|---|---|
| Architecture | What matching throughput and latency has the order book sustained in production | Benchmark figures with no production deployment behind them |
| Resolution | Which data sources settle each category, and who holds final authority in a dispute | “Trusted data feeds” with no named sources |
| Settlement | How long after event conclusion do payouts clear | No stated figure |
| Market control | Can the operator create and configure markets without vendor involvement | Market creation handled as a support ticket |
| Compliance | Which controls are native, which are third-party, and what is the operator’s contracting burden | Compliance described as fully handled |
| Customization | What is configurable versus what requires custom development at additional cost | Broad customization claims without a scoped list |
| Support | What are the response commitments during live events and settlement windows | Business-hours support for a product that peaks on weekends and election nights |
| Exit | What data and market history is portable if the operator migrates | No portability provision |
The concentration of prediction market activity around scheduled events makes support commitments unusually important. A venue that degrades during a championship final or a rate decision loses the traders it spent months acquiring.
Common Reasons Predict Market Launches Stall
Launches rarely fail on technology. They fail on the items that sit outside the vendor contract.
- Licensing started too late. Technical integration completes and the venue cannot legally open in its target market.
- No liquidity plan. The platform goes live with no resting depth, spreads are unusable, and early traders do not return.
- Overextended market catalogs. Fifty thin markets perform worse than five deep ones and multiply resolution risk.
- Ambiguous contract language. Resolution criteria written loosely produce disputes that damage credibility faster than any outage.
- Acquisition treated as a later problem. Operators without an existing user base consistently underestimate the cost of building one from zero.
Deploying with ChainUp Enterprise-Grade Prediction Infrastructure
ChainUp’s white label prediction markets infrastructure, Hermes, is built around the properties that decide whether a venue holds volume:
- The order book has to hold under pressure. Hermes runs a central limit order book with sub-millisecond execution designed to maintain tight spreads through 100x traffic surges — championship finals, rate decisions, election nights. That is what attracts the professional market makers who supply most of the resting liquidity, and without them the venue cannot sustain the spread discipline that event contracts demand.
- Settlement has to be fast and defensible. The resolution disputes that have trapped tens of millions on major venues — Polymarket’s $60M Bitcoin dispute, the $7M Ukraine mineral deal — are infrastructure failures, not edge cases. Hermes settles automatically through oracle verification the moment an event concludes, against the one-to-six-hour delay common across the industry. Operators define the resolution rules per market, and every settlement produces an audit trail.
- The compliance layer has to work across jurisdictions. The CFTC framework is still proposed rulemaking, not final. Operators building now need infrastructure that adapts when the rules change. Hermes ships with KYC, transaction monitoring, geo-fencing, and audit controls configurable per jurisdiction, backed by ChainUp’s SOC 2 and ISO certifications.
Everything else — gasless trading UX for mainstream adoption, curated market creation across sports, macro, politics, and commodities, full brand control through a centralized admin suite, and built-in liquidity frameworks from day one — is deployed in a branded venue live in weeks, not the nine to eighteen months of an in-house build.
Operators targeting markets live before the NFL playoffs in January should start scoping now. Talk to the ChainUp team for a demo of Hermes.
Frequently Asked Questions
What is the difference between a prediction market and a sportsbook?
A sportsbook sets odds and takes the other side of the bet, profiting from the margin built into those odds. A prediction market matches traders against each other and earns fees on the activity, with prices set by participants rather than by the house. Positions on a prediction market can also be sold before the event resolves.
How much does it cost to build a prediction market platform?
Published estimates put in-house development at roughly $80,000 to $500,000 or more over six to nineteen months, before licensing. A U.S. exchange registration adds legal fees, capital covering more than a year of operating expenses, and a review process that has recently run beyond two years. White label deployments remove most of the software cost and launch in weeks.
How long does a white label prediction market deployment take?
Vendor timelines across the market range from roughly one week to several weeks for technical deployment. The realistic end-to-end timeline is longer, because licensing, liquidity arrangements, and compliance configuration typically run longer than the integration itself.
Do operators need a gaming license to run a prediction market?
It depends entirely on jurisdiction. In the United States, event contracts are regulated as derivatives by the CFTC rather than as gaming products. Several other jurisdictions classify them as gambling and require a gaming license, and some prohibit them. Legal review per target market is required before launch.
What happens when an outcome is genuinely disputed?
That depends on the resolution design. Optimistic oracle systems escalate to a token-holder vote, which has produced contested results in high-value markets. Platforms settling against named objective sources such as official league data resolve disputes by reference to the source. Clear contract language and a documented escalation path reduce the frequency of disputes more than any mechanism resolves them well.
Can a white label platform integrate with an existing exchange or app?
API-first platforms are built for this. They connect to existing identity verification, balance management, and payment systems so traders access event markets inside the product they already use, without a separate account or a separate funded balance.
Which market categories generate the most volume?
Sports dominate on a volume basis, accounting for the large majority of activity on the biggest venue and the largest single category elsewhere. Politics, macroeconomic indicators, and crypto prices follow, with volume concentrating sharply around scheduled events such as elections, rate decisions, and championship finals.
