3 posts tagged with "displacement"

What happened. DraftKings has moved its web DFS product in New Jersey from GeoComply to Radar.

What stayed. The DraftKings Sportsbook and the DraftKings mobile apps remain on GeoComply. This is a partial-displacement, not a wholesale loss.

Open question being tested. Whether running two different geolocation providers side by side introduces compliance or security gaps — internal ticket CIV-65: DraftKings DFS - validate the competitor's integration.

Why it matters. This is Radar's first major US live-traffic win on a Tier-1 operator. The sales narrative is two-sided:

• Concerning: DK's procurement team has now signed off on Radar for a regulated US product. Other operators may treat this as permission.
• Constructive: The pattern "challenger gets the DFS web slice, GeoComply keeps everything else" is the new template for second-source attempts. Lead with "we keep the high-stakes stuff" in displacement conversations.

Counter-evidence. Radar's compliance gaps across other operators (rooted-hidden Android, resigned iOS, GPS simulator, jailbroken iOS at Sleeper/PrizePicks/Fliff, Chrome extension at Underdog) are independent of this migration and should be in every DK-adjacent conversation.

Radar profile →

What we confirmed. Splash Sports (DFS) is planning to offload XPoint in June 2026. Reported in the Apr 7 weekly research and reconfirmed Apr 14.

The reason. Splash Sports runs DFS game modes that have different state-by-state availability. XPoint requires the operator to build the multi-state handling themselves — there is no XPoint product equivalent of:

• GeoComply Multipass — one integration, many regulated jurisdictions.
• GeoComply Dynamic Boundaries — operator-configurable boundary logic per game / per state.

Why it matters. This is direct sales evidence that XPoint's developer-friendly auth model (clientKey per session, no expiry, JWT, auto re-geolocation, jurisdictionArea field in response) does not actually solve the multi-jurisdiction problem. Lead with this in any DFS RFP conversation.

Action. Confirm Splash Sports as a GeoComply opportunity for the June 2026 offload window. Use the Splash Sports narrative in any operator conversation where XPoint is being evaluated for a multi-state product.

Xpoint profile →

What happened. TQJ (Todos Querem Jogar / Bet do Milhão), backed by Grupo Silvio Santos, had been part of OpenBet's Brazil launch cohort. Reported in two consecutive weekly syncs (Apr 7 + Apr 14): TQJ switched OpenBet off, citing "worked poorly and caused UX issues."

Current state. TQJ is now running on IP-only as their primary geolocation. No proper geo-enforcement in a regulated market.

Why it matters. A paid OpenBet customer chose IP-only over OpenBet Locator. That's the strongest possible product-quality signal we get from the market — and it's a sales-ready data point for any Brazil operator conversation. The May 5 monthly brief confirms TQJ remains off the product.

Adjacent narrative. BandBet (the other Brazil launch client) and 200+ non-geo OpenBet platform clients are still on the platform — the threat is not OpenBet leaving Brazil, it's OpenBet bundling Locator into platform deals where the operator doesn't know what they're getting.

OpenBet profile →