Italy ADM Roadmap
Netbet Italy · Digitain platform · stakeholder briefing · 18 November 2026

From regulation to go-live

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.

Set by rule written in the regulation Estimate average of industry sources Not published nobody has given a figure yet

The short version

Nov 2027 to Oct 2028

Realistic go-live window

For the Digitain platform in Italy. The central case is about May 2028, roughly 17 months from today.

4.5 to 9 months

Development is the largest unknown

The product teams have not sized the work yet. Every month of development moves every later date by a month.

3 waits

Outside our control

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.

1. What ADM requires, by platform area

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 areaWhat ADM requiresSet byMessage to ADMWhat the lab checks
Player site and appsItalian language, age and responsible-gaming notices, limit and self-exclusion tools, session time-out.Technical Rules, concession agreementNo 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 accountAccount 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 contractPACG 3.3Identity data, limits, self-exclusion and account states, and 10-year retention.
Sports bettingEvents created at ADM. Each bet sent to ADM and accepted and debited only after ADM returns the ticket ID.Technical RulesPSQF 5.2Bet flow, settlement, cash-out, results.
Virtual sportsSchedule and events opened at ADM. The virtual platform is verified by Sogei.Technical Rules, Sogei procedurePSV 2.0Only the integration with the rest of the system.
Horse racingOnly races and bet types of ADM's official programme, fixed odds only.Technical RulesPSIP 3.0Bet flow and settlement.
Casino and card gamesGame 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 decreePGDA 3.1.0Session flow, random number generator, payout and game rules.
Integrity checksDigests 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 guidelinesPACG 6.7Game protocolsThe check system itself, and the digests the lab issues for every critical file.
AccountingFigures per game type that match ADM's own. The platform requests ADM's accounting statements and reconciles each day.Technical RulesPSQF 8000/8001PSV 9200PSIP 3500/3600PGDA 800That the figures reconcile with ADM's.
Back office and reportsADM can query all stored data for any period it defines. Results within 48 hours, exportable. Account reports on request.Technical RulesNo messageThe reports end to end, on complete platform data.
Link and securityDedicated 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 manualsCarries every messageConnectivity and message security with Sogei's test environment.
Hosting and continuityInfrastructure in the European Economic Area. Data encrypted in transit and at rest. Disaster-recovery copy at a separate site within 120 seconds.Technical RulesNo messageDocuments 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.

2. The path to go-live

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.

  1. 1

    Gap analysis and grooming

    Digitain complianceProduct teamsAbout 2.5 months: Nov 2026 to Jan 2027
    • Every requirement is compared with what the platform already does.
    • Gaps become change tickets. Product teams review them, ask questions, and the tickets are groomed again.
    • Open questions go to Netbet, because ADM leaves some measures to the operator.
  2. 2

    Implementation

    Digitain product and tech4.5 to 9 months from February 2027
    • Build the five protocol adapters, the integrity check, the reconciliation and the missing platform functions.
    • Test against Sogei's test environment, which Sogei makes available before the certification request is filed.
    • Prepare what the lab needs: technical report, annotated source code, reproducible builds, list of critical files.

    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.

  3. 3

    Certification request and lab selection

    Netbet filesDigitain suppliesLab queue: 2 to 8 weeks
    • Netbet chooses one of ADM's verification bodies and files the request in ADM's reserved area.
    • The lab is not chosen yet. The queue is the first wait, so the lab should be booked during development.
  4. 4

    Lab verification and Sogei protocol tests, in parallel

    Verification bodySogeiDigitainLab testing: 3 to 6 monthsEach Sogei session: 1 working week
    • The lab checks the whole system: source code, documents, every component, the site and apps, communication between components and with ADM, game rules and the random number generator.
    • Each Sogei test session must finish within one Monday to Friday week and pass every point. One failed point means a complete new session.

    The lab sends its result to ADM only when the whole system has passed.

  5. 5

    ADM review and certification

    ADMReview time not publishedPlanning allowance: 4 to 12 weeks
    • ADM checks that the lab's work is complete and regular, then issues the certification by certified e-mail.
    • The allowance comes from other regulators. ADM has published no figure for this step.
  6. 6

    ADM production check

    ADMNetbetDigitainAt least 5 days' notice
    • Done in the live environment, once per game type: sales, bet acceptance, accounting, crediting of wins, payments and messages to ADM.
    • Five test accounts held by a company are registered and their schedules published beforehand.
    • Faults found are fixed before a repeat check.

    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.

  7. 7

    Go-live and changes afterwards

    NetbetDigitain
    • The system must run exactly as certified.
    • A change to a critical file or a new function goes to the lab first. Releases of such changes wait for its answer.
    • Secondary sources report that an emergency fix may go out first, provided the lab certifies it within two weeks. To be confirmed.
  8. +

    Parallel Netbet track: reports and responsible-gaming measures

    NetbetADMReview time not published
    • Netbet updates its technical report to ADM and, where the tools change, resubmits its responsible-gaming measures, which ADM assesses in advance.
    • Digitain supplies the descriptions of its functions. This must be ready before step 3.

    Whether the migration needs a fresh ADM assessment of the responsible-gaming measures is still to be confirmed with Netbet.

3. A realistic calendar

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.

Fast case: 12 monthslive about Nov 2027
Central case: 17.5 monthslive about May 2028
Slow case: 22.6 monthslive about Oct 2028
04812162024 months
Gap analysis and grooming Development Lab queue Lab testing ADM review Production check
StageFastCentralSlowBasis
Gap analysis and grooming2.5 months2.5 months2.5 monthsEstimate Allows for two review rounds with the product teams.
Development4.5 months7 months9 monthsEstimate, low confidence To be sized by the product teams.
Development completeabout Jun 2027about Sep 2027about Nov 2027
Lab queue2 weeks5 weeks8 weeksEstimate Industry sources give 2 to 8 weeks.
Lab testing, full platform3 months4.5 months6 monthsEstimate Industry sources give 3 to 6 months. Sogei sessions run inside this window.
ADM review of the lab result4 weeks8 weeks12 weeksNot published Allowance borrowed from other regulators.
Production check2 weeks2 weeks2 weeksSet by rule 5 days' notice, plus our own allowance for preparation.
Go-liveabout Nov 2027about May 2028about Oct 2028Fixes 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.

4. What could move the dates, and what is still open

Could add time

  • A failed Sogei point restarts the whole session.
  • A failed lab test or maths model adds weeks and a new submission.
  • Game providers each use their own lab, and shared components must be certified first.
  • Rules still to be issued by ADM, such as the provision on accepted digital ID tools.
  • Open scope questions: who provides the virtual sports platform, and whether casino games still need ADM's per-game authorisation.

Could save time

  • Components already certified in Italy, such as providers' game platforms, need only an integration check.
  • Booking the lab before development ends.
  • Complete documents on day one, so the lab does not send the submission back.
  • Starting the Sogei protocol tests as each adapter is ready, instead of at the end.

To confirm before these dates go on a plan

  • Development effort, sized by the product teams.
  • Which verification body Netbet will use, and its real queue and quote.
  • How long ADM takes to review a lab result, and to assess responsible-gaming measures. Ask ADM or the lab.
  • Whether the Digitain migration is handled as a new certification or as a change to Netbet's certified system, and whether the production check repeats.

Sources

Process. ADM operating instructions of 7 August 2026 on certifying the concessionaire system, as reported by Agimeg and Agipronews. agimeg.it: ADM certification procedure, August 2026 agipronews.it: ADM operating instructions Rules. ADM Technical Rules, verification-body guidelines (336762/RU), Sogei communication verification procedure v1.2.1, concession agreement No. 16021, as recorded in the project register. Lab and integration durations. Industry guides and a law-firm note, not Italian lab data: licencegaming.com, igaminghub.app, incorpore.ro, vlolawfirm.com, and a vendor claim of 18 to 24 weeks for a build. licencegaming.com: platform certification guide igaminghub.app: certification timelines and costs Emergency fixes after certification. Wizards, 8 October 2026, summarising ADM's August instructions. Secondary source.