How to pass GLI-19 without rewriting the architecture and simplify scaling: SharksCode case
For a B2B platform in iGaming, every scaling means new integrations: game providers, payment services, KYC, local regulatory requirements. In such a dynamic, the architecture quickly becomes overgrown with exceptions.
«Without standardization, each new partner or jurisdiction requires separate custom solutions — in logic, integrations, reporting, access. Instead of a unified architecture, exceptions appear in the code and dependence on a specific market,» explains SharksCode CTO Igor Morgunov.
The team faced a typical industry challenge: in the short term, customization speeds up launch, but in the long term, it makes the system fragile. A solution was needed that would discipline the architecture. GLI-19 certification was that solution.
For a B2B platform in iGaming, every scaling means new integrations: game providers, payment services, KYC, local regulatory requirements. In such a dynamic, the architecture quickly becomes overgrown with exceptions.
«Without standardization, each new partner or jurisdiction requires separate custom solutions — in logic, integrations, reporting, access. Instead of a unified architecture, exceptions appear in the code and dependence on a specific market,» explains SharksCode CTO Igor Morgunov.
The team faced a typical industry challenge: in the short term, customization speeds up launch, but in the long term, it makes the system fragile. A solution was needed that would discipline the architecture. GLI-19 certification was that solution.
REFERENCE
SharksCode is a Ukrainian licensed IT company that creates effective and reliable innovative services. The company specializes in developing high-tech software solutions and platforms in B2B, in particular in the iGaming sector.
Solution: Verify architectural maturity with an independent audit
GLI-19 is a technical standard for interactive gaming systems that tests not the interface, but the foundation: responsible gaming, access control, and proof of actions. Certification is carried out by an independent laboratory. The company does not influence the audit process — it only prepares the platform for verification.
The preparation at SharksCode lasted about four months. The key point of the case: the architecture did not have to be rewritten. DevOps processes, release management, and code review culture already met the requirements of the standard.
«We were already working within the logic of controlled changes, access segregation, and documentation of procedures. GLI-19 did not become a revolution — it became confirmation that these processes really work systematically,» comments Chief Information Security Officer Oleksandr Matsera.
Process: what exactly did the auditors check?
GLI-19 focuses on three critical areas. The first is game integrity: RNG architecture, RTP control, and the inability to change game parameters.
The second is the calculation logic. This is where the greatest number of risks are concentrated. «The architecture must ensure that the flow is reproducible and observable. It is impossible to „draw“ the balance or lose a transaction due to load,» explains Macera.
This includes, in particular, the atomicity of transactions, protection against duplication, and correct rollback mechanisms. The third zone is control and provability: environment segmentation, trust boundaries, minimum required access, MFA for administrators, immutability of logs, and the ability to replay any action in the system.
The system must not only work correctly — it must meet the auditor’s standards.
Result: simplified integrations and reduced contractual risks
The most noticeable changes became noticeable after obtaining certification. Before GLI-19, each new integration was actually accompanied by a local audit: a deep check of the test environment, additional security questionnaires, extended guarantees.
Once certified, the underlying technical risks are already confirmed by an independent laboratory. This reduces the amount of additional testing, speeds up negotiations, and simplifies entry into regulated jurisdictions.
«We may meet the standard at a specific point in time, but no one knows about it. Certification is needed to guarantee the immutability of key responsibility criteria,» Morgunov notes.
Certification as a tool of engineering discipline
SharksCode emphasizes: GLI-19 does not make the system invulnerable. But it removes a class of critical risks — game integrity, access control, and provability.
And most importantly, it prevents scaling from destroying the architecture from the inside. «GLI-19 is primarily a way to prevent the system from becoming fragile during scaling,» Morgunov summarizes.
«AI will get smarter if the speed of light is enough to transmit signals in chips.» CMO, STO and Art Director SharksCode on the prospects of AI and smart tools that make work easier in IT
