DANIEL WHITELEY Chief Technology Officer
Tere's always a little bit of tech debt, but we're built on an event- driven microservices architecture. We get all the benefits of this architecture ensuring that our components are loosely coupled. We can make change quickly, have high levels of resiliency, and we can scale. Our platform has been designed from the ground-up in terms of performance and, crucially, security.
Our goal is to continually make things easier for our end customer, driving operational efficiencies and layering high levels of personalisation and relevancy around that. Tat is the next evolution of what we want to achieve in terms of our campaign management.
Taking a holistic view of the portfolio, what's your assessment of Bede Gaming's offering as a platform provider?
Jess: What we’ve recognised from discussions that we’ve had with prospective customers in various markets is that they're looking for flexibility in a platform and getting real value add on a continuous basis. Where Bede differentiates from legacy platforms in the industry is that we have an open-source platform. It's a single code base meaning customers have access to all our tools. From a product perspective, our role is to ensure that everything is configurable so customers can tailor things to their markets. Resultingly, we release features every two weeks. Tis means customers are constantly getting that value add they're after. We demo possibilities about how they can manage their players better and gamify experiences.
As a platform and software provider, another thing that we focus on is building great partnerships with our customers. Some customers have felt less heard from other platform providers, whereas we mould our processes to suit their needs and take the time to understand their core ambitions, developing a product roadmap around their markets and how they operate. Our customers enjoy the flexibility of the Bede platform, its scalability from a technical standpoint and how we adapt our approach to suit their ways of working.
Dan: Tere's always a little bit of tech debt, but we're built on an event-driven microservices architecture. We get all the benefits of this architecture ensuring that our components are loosely coupled. We can make change quickly, have high levels of resiliency, and we can scale. Our platform has been designed from the ground-up in terms of performance and, crucially, security. Security is often thought about as a bit of an afterthought. With Bede, it's built into the core platform.
We're cloud native by default. Microsoft is our partner for how we 68
host and deliver our services which is great because it allows us to leverage all the benefits of cloud and run at a base level. Tis means that when there's a large event or big ticketing opportunity, we can then scale up using modern technologies like Kubernetes to assist. We're also leveraging some of the best open-source, open-standards databases on the market such as MongoDB and Postgres. Tey're also cost-efficient. It's great to have a high performing infrastructure, but if it's coming at a price tag that is premium, often for a lot of our customers that's a challenge.
Our goals in terms of what we're doing from a tech strategy are around how we deliver a performant, highly available, fault tolerant service at the best possible price point. Tat's a combination of how we set up our architecture and the underlying technology that we're using. Ultimately, we've got a very resilient infrastructure and set of services. And then from an information security point of view, there's layers of protection around our systems which allows us to have a robust security posture out there in the market. Our end customers benefit from this because we're secure by design and with the ever- changing threat landscape it's something that is high on the agenda. Security is not a tertiary thought at Bede. It's primary and secondary in our mindset. It's foremost in our minds to ask ourselves with every line of code – “when we deploy that, how are we protecting customer and player data?”
What's the roadmap for 2025?
Jess: I'm very excited about some of the things we've got coming. For us, this year is focused on how we gamify and diversify the personalisation elements on our platform. We've mentioned Dynamic Segments and that's just the initial phase. We've got a full suite of new enhancements being built on top following active feedback, iterating on the product and improving throughout the rest of 2025.
We're eager to go to various trade shows this year to continue to demo the product and demonstrate the progress being made. We have nearly finished development to launch the first iteration of a tournaments and leaderboards tool. Tis is an in-house product that allows customers to set up different tournaments and competition-
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 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142
