For the product, technology, compliance and Netbet teams: what ADM requires of the platform, the steps between a finished build and live play, and a realistic calendar. Netbet already operates in Italy on its current provider, so no licence deadline drives this plan. The pace is set by development and by waits outside our control.
For the Digitain platform in Italy. The central case is about May 2028, roughly 17 months from today.
The product teams have not sized the work yet. Every month of development moves every later date by a month.
The test lab's queue, ADM's review of the lab result, and ADM's scheduling of the production check. We can prepare for them but not speed them up.
Each row is a part of the platform. It shows what ADM requires, which document sets it, which message carries it to ADM, and what the verification lab checks. The documents are: the Technical Rules, the concession agreement, the gaming-account contract, the verification-body guidelines, the casino game decree and the protocol manuals.
| Platform area | What ADM requires | Set by | Message to ADM | What the lab checks |
|---|---|---|---|---|
| Player site and apps | Italian language, age and responsible-gaming notices, limit and self-exclusion tools, session time-out. | Technical Rules, concession agreement | No message The site's integrity digest goes through PACG. | The site and apps behave as the rules describe, on devices as well as the web. |
| Gaming account | Account opened at ADM before activation. Login checked with ADM at every session. Every deposit, withdrawal, bonus and reversal recorded at ADM before the balance moves. Limits, self-exclusion and account states kept in step with ADM. | Technical Rules, gaming-account contract | PACG 3.3 | Identity data, limits, self-exclusion and account states, and 10-year retention. |
| Sports betting | Events created at ADM. Each bet sent to ADM and accepted and debited only after ADM returns the ticket ID. | Technical Rules | PSQF 5.2 | Bet flow, settlement, cash-out, results. |
| Virtual sports | Schedule and events opened at ADM. The virtual platform is verified by Sogei. | Technical Rules, Sogei procedure | PSV 2.0 | Only the integration with the rest of the system. |
| Horse racing | Only races and bet types of ADM's official programme, fixed odds only. | Technical Rules | PSIP 3.0 | Bet flow and settlement. |
| Casino and card games | Game session opened at ADM. Each amount moved into a session accepted before play. Rounds reported at least daily. Minimum payout and game rules set by decree. | Technical Rules, casino game decree | PGDA 3.1.0 | Session flow, random number generator, payout and game rules. |
| Integrity checks | Digests of the installed software sent to ADM daily and after each patch. A component that keeps failing is blocked after 15 calendar days. | Technical Rules, verification-body guidelines | PACG 6.7Game protocols | The check system itself, and the digests the lab issues for every critical file. |
| Accounting | Figures per game type that match ADM's own. The platform requests ADM's accounting statements and reconciles each day. | Technical Rules | PSQF 8000/8001PSV 9200PSIP 3500/3600PGDA 800 | That the figures reconcile with ADM's. |
| Back office and reports | ADM can query all stored data for any period it defines. Results within 48 hours, exportable. Account reports on request. | Technical Rules | No message | The reports end to end, on complete platform data. |
| Link and security | Dedicated line or VPN to Sogei, redundant, in Netbet's name. Each protocol's own signature. All components on one UTC time source. | Technical Rules, protocol manuals | Carries every message | Connectivity and message security with Sogei's test environment. |
| Hosting and continuity | Infrastructure in the European Economic Area. Data encrypted in transit and at rest. Disaster-recovery copy at a separate site within 120 seconds. | Technical Rules | No message | Documents and a functional check of the recovery set-up. |
Out of scope for this project: retail, bingo, pool betting, betting exchange and poker tournaments. A separate page shows the same areas as an architecture diagram next to the platform's services.
Each step starts only after the one before it, except where a step says it runs in parallel. Betting cannot open before step 6 is complete.
Low confidence. Industry sources give 3 to 6 months for the technical integration and 18 to 24 weeks for a vendor build, and our gap list is large, so the range runs higher. The product teams must size it.
The lab sends its result to ADM only when the whole system has passed.
Bet collection may start only after certification and a positive production check. Whether the check repeats for a platform migration is still to be confirmed.
Whether the migration needs a fresh ADM assessment of the responsible-gaming measures is still to be confirmed with Netbet.
Months counted from today, 18 November 2026. Fast, central and slow cases use the low, middle and high end of each range. The lab figures are industry averages for full platform certifications, and no source gives Italian lab times, so treat the dates as planning guidance. Development is the least certain input.
| Stage | Fast | Central | Slow | Basis |
|---|---|---|---|---|
| Gap analysis and grooming | 2.5 months | 2.5 months | 2.5 months | Estimate Allows for two review rounds with the product teams. |
| Development | 4.5 months | 7 months | 9 months | Estimate, low confidence To be sized by the product teams. |
| Development complete | about Jun 2027 | about Sep 2027 | about Nov 2027 | |
| Lab queue | 2 weeks | 5 weeks | 8 weeks | Estimate Industry sources give 2 to 8 weeks. |
| Lab testing, full platform | 3 months | 4.5 months | 6 months | Estimate Industry sources give 3 to 6 months. Sogei sessions run inside this window. |
| ADM review of the lab result | 4 weeks | 8 weeks | 12 weeks | Not published Allowance borrowed from other regulators. |
| Production check | 2 weeks | 2 weeks | 2 weeks | Set by rule 5 days' notice, plus our own allowance for preparation. |
| Go-live | about Nov 2027 | about May 2028 | about Oct 2028 | Fixes and repeat test sessions add time and are not included. |
Booking the lab during development can take the queue off the critical path, which would bring each date forward by up to two months. Lab queues may also be longer than the averages if many operators file at the same time. That is our reading, not an ADM statement.