Who holds the game, the cashier and the support desk

Ask who actually runs an account at this end of the market and the answer is rarely a single company sitting alone on its own codebase. Most of the offshore-facing market is assembled rather than built: a brand signs onto a platform stack and rents the parts that make an account work, from the game catalogue to the wallet to the queue that reviews a withdrawal. The brand owns the logo, the welcome page and the bonus copy. The stack owns the machinery underneath, and whoever operates the stack holds the levers that matter.

An independent build inverts that arrangement. The operator commissions or writes its own stack, runs its own cashier, staffs its own support desk and answers for all of it with no platform layer in between. Nothing about the games themselves has to change: the same studio titles can appear on either kind of setup and the reels spin at the same speeds. What changes is custody. On a platform, custody of the money flow, the verification checklist and the complaint file is shared infrastructure. On a standalone build, every piece of it sits with one operator whose name is on the door.

The chart below draws the split as this page models it. We treat roughly 71% of the offshore-facing market as platform-served and roughly 29% as standalone, figures chosen as a working assumption for illustration rather than a measured census: no public register counts stacks, and this site declines to invent precision it cannot cite. The direction is the point. A reader arriving at this end of the market is, on the model, likelier to land on rented machinery than on owned machinery, and the minority who land on a standalone build meet something far less standardised, sometimes to their benefit and sometimes the opposite.

The distinction earns its space because every protection or friction a player cares about lives in the machinery rather than the logo. Whether a withdrawal is reviewed in hours or in days, whether terms read like one template or like somebody’s own drafting, whether a complaint has anywhere to climb: all of that follows the stack, and the sections below cost out what each arrangement hands over and what it withholds.

What the platform route standardises for the reader

The platform route sells consistency, and a reader feels it within minutes of arriving. The cashier screens look alike from brand to brand because they are the same screens. The verification checklist follows one script, so the documents requested and the order they are requested in repeat across skins. The bonus template repeats too: the same match shape, the same wagering arithmetic, the same maximum-bet clause reprinted under a different logo. Support replies come from a desk staffed for the whole stack, so the tone and the scripts sound similar wherever an account was opened.

Standardisation has honest value. Reading cost drops, because a player who has read one set of platform terms has, in effect, read the family. Familiarity lowers friction at the cashier, where the same deposit screens, the same rail presentation and the same withdrawal form appear wherever the reader goes next. When a platform revises a process, every skin on the stack moves with it, so there is no scenario in which one brand’s verification flow quietly lags behind another brand’s.

The British regulated market runs a stricter version of the same logic by design. Licence conditions standardise what every licensee must do, from age and identity verification to stating the protection level that applies to customer funds, so consistency there is enforceable rather than merely convenient. At the offshore end, consistency is a commercial preference. It costs the reader little while everything runs smoothly, and it costs a great deal the day something does not, because a shared template also shares its blind spots: where the template’s dispute wording is weak, it is weak everywhere it has been reprinted.

None of this tells a reader which arrangement a particular brand uses, and this page will not pretend to a census it cannot cite. What it does is price the two arrangements so the difference is legible before a deposit rather than after. The next section takes the standalone side of the model and sets out what actually changes when the machinery belongs to the brand itself.

What independence changes: rules, clocks and dispute routes

Independence here does not mean independence from rules; it means a change of author. A standalone operator writes its own terms, and the drafting shows: clause order differs, the wagering arithmetic is presented its own way, and the wording on dormant accounts, maximum bets and document requests comes from an in-house pen rather than a shared template. For a reader that makes the reading real. Terms at this end of the market have to be read on their own merits, on the operator’s own page, because generalising from a sister brand is precisely the mistake the platform model forgives and the standalone model punishes.

Clocks change as well. A payout window on a platform tends to be a platform number, uniform across the family. On a standalone build the window is whatever the operator’s own cashier team delivers, and the windows printed across this page’s comparison rows run from a few hours on the crypto-leaning rows to five banking days at the top of the card-route range. That spread is the visible price of independence: variety in both directions, faster in places, slower in others, and rarely any way to know which applies until the terms have been read line by line.

The dispute route changes most of all. On a platform a complaint can climb: brand first, platform layer second, licensing jurisdiction after that. On a standalone build the operator is the first stop and, in practice, the last, because an offshore licence brings no entry in the Gambling Commission’s public register, no UK dispute route and none of the fund protection levels a UK licence mandates. A UK licence, by contrast, obliges a licensee to affiliate with an alternative dispute resolution provider, so a complaint has a free escalation route once the operator has given its final answer. Independence without that scaffolding leaves the operator’s own complaints process carrying all the weight.

There is a fair case for the other side. A standalone operator that wants to compete on service has to build the service itself, and some plainly try: quicker crypto rails, payout queues sized in hours, terms drafted to be read rather than skimmed. The honest summary is variance. Independence removes a floor and a ceiling at once, and the reader inherits the whole spread between them.

A session model with the assumptions in the open

Ownership questions stay abstract until they are costed, so this section costs the play itself and leaves the wrapper to the sections around it. The calculator below runs a session model: a £100 bankroll, £1 stakes, a house edge input of 2.7% and four sessions. The edge is a working assumption, an input rather than a measurement of any particular game or lobby, and the model runs the same arithmetic with any figure substituted in its place.

At a 2.7% edge, expected loss is 2.7p for every £1 turned over, fixed before the first stake and untouched by anything the session feels like doing. Turnover itself depends on game speed and on outcomes, which is why the model works from stakes and session count instead of pretending to know how many rounds an evening contains. Across four sessions the arithmetic simply repeats: the same rate applies to each pound staked, the expected cost accumulates with turnover, and the variance around that expectation can swamp it entirely inside a single sitting. An expected value is a long-run average, never a forecast of an evening, and this page presents it as a model for exactly that reason.

What the model deliberately leaves out is the wrapper: who reviews the withdrawal, who answers the support ticket, where a complaint goes when the first answer is no. Those are ownership questions, and the calculator has no input field for them, which is rather the point of the surrounding sections. The same session model produces the same expected cost at a UKGC-licensed site and at an offshore one, because the edge comes from game rules rather than from who owns the stack. The difference between the two sits entirely in the machinery around the play, and that machinery is what the licence column in the comparison rows beneath is there to keep visible.

One habit makes the model more useful: change a single input at a time and watch which one moves the answer. Bankroll and stakes set the pace of turnover; the edge sets the price of each pound turned over; the session count sets how many times the price is paid. Ownership, the subject of this page, sits outside the form entirely, which is why the page keeps returning to it in prose.

Function by function: platform stack against independent build

The two arrangements reduced to the five functions a player actually touches. What follows is the page’s own apparatus, a conceptual model of where custody sits, not a survey of named brands; the named comparison arrives in the section after this one.

Two rows carry extra weight. The dispute row is where the platform model quietly earns its keep, because a second layer to complain to is worth something even when nothing obliges it to help. The self-exclusion row is where the licence model earns its keep instead: where a UK licence applies, the operator must run a facility of its own alongside the national scheme, and no shared template can be the reason such a facility is missing.

Twelve rows: offshore builds beside the British baseline

The table beneath puts six offshore rows beside six UKGC-licensed baselines, drawn from the ranges compiled on this site at the time of writing. Each row carries its licence class first, then the welcome band, the wagering multiplier, the minimum deposit, the payout window and the payment rails. The baseline rows exist to show what the British regulated version of the same functions looks like, not as offers that carry across; the note under the table says as much. Read the licence column before anything else, because everything else on a row inherits from it.

Figures are category-typical ranges compiled from operator-published terms at the time of writing, not quotes of any single promotion. UKGC-licensed rows are the British baseline shown for comparison; none of them are claimable at the offshore offers modelled on this page. Verify every term on the operator’s own page before you take it.

Notice what repeats and what does not. The offshore rows cluster around a similar multiplier band and a similar deposit floor, because this end of the market copies what sells; the spread shows up in payout windows and rails, where independence does its work. The baseline rows scatter further on wagering, from multipliers that mirror the offshore band to bingo products priced on an entirely different scale, which is what a crowded domestic market with standardised player protections looks like when laid out on one table.

What a UK licence would have bought, and where the scheme stops

A UK licence is the missing column on the offshore rows, and the package it would have carried deserves a plain listing. Providing remote gambling facilities to people in Great Britain requires an operating licence from the Gambling Commission, and the licence arrives as a bundle: an entry on a public register anyone can search, customer funds held at a stated protection level, age and identity verification as a condition of licensing rather than a courtesy, an obligation to affiliate with an alternative dispute resolution provider, and a regulator that can fine, suspend or revoke when the conditions are breached. Self-exclusion is doubled up: a licensed operator must offer a facility of its own in addition to the national scheme, and must follow licence conditions on customer interaction and product design while it does so.

The national scheme is GamStop: free, covering every GB-licensed online gambling operator, with exclusion periods of six months, one year or five years that cannot be lifted before the chosen term ends. The scheme’s coverage follows UK licensing rather than where the player lives, and that is the sentence that decides this page’s subject: an account at an offshore operator is not covered, whatever the player’s postcode. A GamStop registration does not follow a reader across to this end of the market, and nothing here will dress that up as anything other than what it is.

At this end, the protections shrink to whatever the operator has chosen to build. Some publish limit tools and cooling-off switches of their own; some publish very little; the licence note printed with this page states the position plainly, because repeating it next to every modelled price is the site’s method. Verify any licence claim a brand makes on the issuing authority’s own register: offshore jurisdictions commonly serving UK-facing brands include Curaçao and Anjouan, Curaçao has been reforming its framework and phasing out the master-licence model, and a register line on file beats a footer badge every time.

That is the price of independence stated without varnish: no scheme coverage, no register entry, no mandated dispute route, no fund protection level, and in exchange, terms and tools that exist at the operator’s discretion. A reader who wants the scheme’s protection has a plain answer waiting, and it is the licensed rows on the comparison table rather than anything modelled on this page.