title: Guernsey — Technical compliance: What must the platform meet? | advennt.io canonical: https://advennt.io/jurisdictions/alderney/technical/ [Jurisdictions](https://advennt.io/jurisdictions/) [Guernsey](https://advennt.io/jurisdictions/alderney/) Technical compliance Guernsey · Question 08 of 11 # Technical compliance: What must the platform meet? Favourable · Probable · AI-generated · [Back to full Guernsey report →](https://advennt.io/jurisdictions/alderney/) Key section parameters | Jurisdiction | Guernsey (GG-ALD) | |---|---| | Regulator | Recorded in register | | Favourability | Favourable | | Confidence | Probable | | Review status | AI-generated | | Last collected | 18 Oct 2026 | Summary answer AGCC requires all eGambling equipment to receive pre-launch approval under the Regulations, and reviews a licensee's internal control systems before go-live. This places a technical-certification gate ahead of commercial launch: a Category 1 or Category 2 licensee must clear its platform, equipment … ## Full section analysis AGCC requires all eGambling equipment to receive pre-launch approval under the Regulations, and reviews a licensee's internal control systems before go-live. This places a technical-certification gate ahead of commercial launch: a Category 1 or Category 2 licensee must clear its platform, equipment and internal control systems with the Commission before taking the product live, rather than certifying on a post-launch or self-certification basis. For an operator building a launch timeline, this pre-launch review is a structural dependency sitting alongside, rather than instead of, the Regulation 243 capital-adequacy test that gates the licence itself.