title: Lithuania — Technical compliance: What must the platform meet? | advennt.io canonical: https://advennt.io/jurisdictions/lithuania/technical/ [Jurisdictions](https://advennt.io/jurisdictions/) [Lithuania](https://advennt.io/jurisdictions/lithuania/) Technical compliance Lithuania · Question 08 of 11 # Technical compliance: What must the platform meet? Mixed · Not recorded · AI-generated · [Back to full Lithuania report →](https://advennt.io/jurisdictions/lithuania/) Key section parameters | Jurisdiction | Lithuania (LT) | |---|---| | Regulator | Recorded in register | | Favourability | Mixed | | Confidence | Not recorded | | Review status | AI-generated | | Last collected | 18 Oct 2026 | Summary answer Remote gambling operators in Lithuania must integrate their systems with the new LAKIS (Slot Machine Control Information System) central monitoring platform by May 2026. This is a probable, fragile-sourced requirement drawn from secondary industry press rather than a primary LPT publication retrieve… ## Full section analysis Remote gambling operators in Lithuania must integrate their systems with the new LAKIS (Slot Machine Control Information System) central monitoring platform by May 2026. This is a probable, fragile-sourced requirement drawn from secondary industry press rather than a primary LPT publication retrieved this cycle, though the LPT's own portal separately confirms the existence of the LAKIS data-submission sub-system. Non-integration with LAKIS by the deadline is flagged as a licence-revocation risk driver, making this a materially higher-stakes technical-compliance obligation than a routine reporting update. Operators should treat the May 2026 date as a hard compliance deadline rather than an indicative target, given the revocation consequence attached to non-compliance.