iGaming Platform Launch Times
A platform can be technically configured while the operator is still unable to take one lawful wager. We separate the seven clocks that determine go-live and compare only named implementations with a defined scope. Product targets and generic market ranges are not converted into launch durations.
Last updated August 20, 2026 · overall-score order, not a speed score
18
providers reviewed
6
named timed cases
5
broad platform cases
13
without a named timed case
One launch date, seven separate clocks
These workstreams can overlap, but they do not inherit one another's completion. The critical path ends only when every mandatory production gate is closed.
| Clock | Starts when | Closes when | Accountable parties |
|---|---|---|---|
| Platform and configuration | Signed scope, environments, integrations, and acceptance criteria | Configured product passes agreed technical acceptance | Provider and operator engineering teams |
| Operating permission | Complete entity, ownership, people, policies, and application file | The exact operator entity can lawfully offer the intended products | Operator, regulator, and advisers |
| Product certification | Frozen product/version and jurisdiction-specific test scope | Required system and game approvals apply to the launch build | Provider, test lab, regulator, and content suppliers |
| PSP and merchant acceptance | Exact entity, license, markets, volumes, methods, and risk file | Deposits, withdrawals, reserves, settlement, and reconciliation pass production testing | Operator, PSPs, banks, and payment orchestrator |
| Content readiness | Contracted studios, titles, territories, wallets, and commercial terms | Approved titles are enabled with correct metadata, limits, and reporting | Operator, aggregator, studios, labs, and regulator |
| Migration and reconciliation | Export rights, field map, cutover population, and rollback rule | Accounts, balances, KYC, limits, exclusions, bonuses, and history reconcile | Outgoing provider, incoming provider, and operator |
| Operational sign-off | Production-like configuration and trained operating teams | Support, risk, finance, RG, incident, reporting, and first-wager controls pass | Operator and contracted managed-service teams |
Named implementation record
Every duration below belongs to the named scope beside it. An isolated sportsbook upgrade is not compared as though it were a greenfield casino, and an incumbent lottery transition is not treated as a new platform build.
| Provider | Named case | Exact scope | Elapsed | Boundary |
|---|---|---|---|---|
| EveryMatrix8.8 | bet-at-home .COM | Full-stack platform migration | 6 months from development start | Germany followed as a separate market extension. The result is one completed implementation, not a standard delivery commitment. |
| EveryMatrix8.8 | Szerencsejáték | Complex regulated turnkey launch | 7 months | Local infrastructure, certification, migration, and launch scope were part of this specific program. |
| Aristocrat Interactive8.1 | Michigan Lottery | Contractual iLottery transition | About 13 months | NeoGames was already the incumbent technology. This is a transition record, not a greenfield platform benchmark. |
| Altenar8.0 | JustBet | Online and retail platform replacement | 3 months after signing | One completed replacement across online and retail channels; it does not establish a portfolio-wide SLA. |
| White Hat Gaming7.1 | VIP Play Tennessee | Already-licensed market replatform | 7 February to 12 May 2025 (about 13 weeks) | The Tennessee project reached go-live. A planned West Virginia extension did not, which keeps market access outside the technology clock. |
| GR8 Tech7.0 | Mojabet | Full turnkey launch | 2 months | The elapsed time applies to Mojabet's defined scope; licensing, migration, and custom work can produce a different critical path. |
Coverage across all 18 providers
No named elapsed-time case means exactly that. It does not mean the provider has never launched a customer or that delivery is slow.
- bet-at-home .COM — 6 months from development start
- Szerencsejáték — 7 months
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
- Michigan Lottery — About 13 months
- JustBet — 3 months after signing
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
- VIP Play Tennessee — 7 February to 12 May 2025 (about 13 weeks)
- Mojabet — 2 months
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
Named elapsed-time case unresolved.
Do not start every clock on contract day
A regulator clock may start only after a complete file, a certification clock after a frozen build, and a PSP clock after the exact entity and transaction profile are accepted.
Keep technology and market access separate
A configured platform, supplier registration, product certificate, and operator permission establish different things. None alone creates a lawful first wager.
Contract the critical path
Name the dependency owner, deliverable, acceptance evidence, delay consequence, rollback point, and excluded third-party time for every launch gate.
Moving an existing player base adds a separate data and operational program. See the platform migration guide and the data ownership and exit-rights comparison, plus the implementation and B2B support comparison, for named delivery and escalation ownership.
Frequently asked questions
How long does it take to launch an iGaming platform?
There is no defensible market-wide duration. Platform configuration, operating permission, certification, payment acceptance, content, migration, and operational sign-off run on separate clocks. The launch date is controlled by the last mandatory gate to close, not the shortest technical target.
Why are product-integration times not treated as casino launch times?
Connecting a sportsbook, aggregator, or content feed can be a bounded technical change. A full launch also has a regulator-facing entity, player accounts, wallet, KYC, payments, responsible-gambling controls, reporting, support, and production acceptance. The scopes are not comparable.
Can a provider guarantee a regulator or PSP date?
No provider controls an external regulator, test lab, bank, acquirer, or independent content supplier. A useful implementation plan names each external dependency, its owner, the complete-file date, the acceptance evidence, and the consequence of delay.
What should an operator put in the implementation schedule?
Use dated gates for scope freeze, environments, data sample, entity and permission, product certification, PSP acceptance, content activation, migration rehearsal, balance reconciliation, training, production acceptance, first wager, hypercare, and rollback expiry. Assign one accountable owner to every gate.