search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
EDWARD SMYSHLIAIEV Chief Technology Officer, GR8 Tech


We do proactive monitoring across the entire platform, so the moment something goes wrong, we already have the tools in place to fix it - often before the customer even notices. We’ve handled massive traffic spikes before, and we’re fully prepared for whatever comes next, whether that’s a World Cup or something completely unexpected.


What role does personalisation play in front-end speed – can tailored experiences actually feel faster to the user?


As a rule of thumb, the more personalisation you have, the more performance degradation you can expect on the front end.


Here’s why: in essence, personalisation creates various builds of the platform and/or more complex architecture. Our platform was initially designed to let the operator change literally anything, create any kind of layouts for different player segments.


We ran analytics and found that, for some brands, there are around 3,000 different layouts, automatically generated through segmentation and configuration in their back end. No developer involved, just the operator ticking a box in the CMS. Tey can create anything to their liking.


A very convenient capability, but it also creates a huge technical challenge. Maintaining performance gets tricky: how do you approach caching, builds, and so on? Te whole market faces this trade-off. We found a shortcut that lets us achieve both: keep full customization capabilities while still advancing toward our main goal of becoming the fastest platform. Te operator changes something, and in seconds it's already on the front end and applied to the player. No trade-off between speed and flexibility - we're proving you can have both.


AI is now a core part of every technology conversation. Where do you see AI having the biggest impact on platform performance?


One of them would be the so-called “copiloting” things - both for players and the operators. Imagine a built-in chatbot much like ChatGPT that helps with various actions across the platform. Let’s say a player is trying to find a good tournament to bet on. AI can give them info on what’s going on with the team or specific players, what events are happening today, what’s trending, and maybe even place the bet automatically from the chat window.


So instead of navigating and trying to find everything on the website, you can just use a chatbot. Same with operators. We have hundreds of


32


different bonuses and configuration options, and managing all of that takes time. So we have an AI assistant integrated - it already exists to a certain extent, though it's not yet making changes as you ask. Tat's where we want to improve: “Create a new type of bonus for this player segment,” and the AI does it for you.


We can see a huge boost there, because operators will need less time spent on operations in man-hours. It becomes easier to use a platform that can be configured in seconds, just in a text window. And for players, it gives more convenience and freedom, saves time, and also impacts retention.


How are you preparing for the massive traffic spikes that global events like the 2026 World Cup will bring?


We’ve had World Cups before, more than once, so we know we’re ready. We still perform regular performance checks and stress tests; in fact, we’re currently running one. We’re making sure we identify any new bottlenecks we might have in our system, but we’re seeing none - so far, so good.


Te last big spike of traffic on our platform was during Usyk vs Dubois 2 in 2025 - a match close to our hearts since we are partners in tech with Usyk's Ready to Fight initiative. Tere was a massive surge, but we had no degradation whatsoever. It went smoothly. So we don’t expect anything bad to happen during the World Cup, we’re fully ready.


And what do you do when something stops working on the platform?


I’m trying to recall incidents like that. Of course, it’s tech, and some things may happen, but we have a great engineering team. We have people online all the time: tech support, infrastructure, and developers - on duty and on shift.


We do proactive monitoring: all our systems are covered with metrics and monitoring. So as soon as something goes wrong, we have tools in place to roll back and fix it immediately, before the customer even notices there were any issues. So, the same as with the World Cup, we are 100 per cent prepared for surprises.


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102