ES
IT
PT
DE
NL
Adam, legacy platforms are a growing concern for operators. Why have they become such a barrier to innovation and growth?
Legacy platforms aren’t the problem in themselves. The problem is that many were built for a very different stage of the industry’s evolution. Over time, new regulations, integrations and commercial demands add complexity, making even straightforward changes harder to deliver. That’s when the platform starts dictating what’s possible, rather than supporting the ambitions of the business. In our experience, operators don’t want to rip everything out and start again – they want an infrastructure that can evolve alongside them as their priorities change.
Blurify describes Openora as an AI-native framework rather than just another platform. What does “AI-native” actually mean, and why does it matter?
There’s a misconception that AI is just another capability you add to an existing platform. It isn’t. AI is already changing the way software is built, so the underlying architecture has to change with it. For us, being AI-native means creating a framework where AI is part of the development process from the outset, helping engineering teams work more efficiently as platforms evolve. It’s not about adding AI for the sake of it. It’s recognising that the way software is developed is changing and building for that reality rather than trying to retrofit it later.
Openora is designed so AI can understand the platform through built-in context and development rules. How does that improve software development compared with today’s AI coding tools?
Today’s AI coding tools are remarkably capable, but they still rely on having the right context. Without it, they can generate code that appears correct but doesn’t necessarily reflect how a platform is structured or why it works the way it does. That’s why we designed Openora so AI can understand the framework itself, rather than simply writing code in isolation. The result is more consistent development and greater confidence that AI-generated changes align with the platform rather than gradually working against it.
Many operators are reluctant to replace their entire platform. Why is incremental modernisation becoming a more practical alternative to full replatforming?
Operators don’t see modernisation as an all-or-nothing decision anymore. Most businesses have invested heavily in their existing platforms and there are often elements that continue to perform well. The question is no longer, “When do we replace everything?” but “What should we improve first?” That’s why incremental modernisation is becoming a far more practical approach. It allows teams to solve immediate challenges, demonstrate value and keep moving forward without committing to a lengthy replatforming project before seeing any real benefit.
How important is a modular, composable architecture for operators looking to launch faster and adapt to new markets?
One of the biggest advantages of a modular architecture is that it reduces unnecessary dependencies. Too often, introducing a new capability means touching parts of the platform that have nothing to do with the change itself. That slows development, increases risk and discourages experimentation. By separating capabilities into clearly defined components, teams can build, test and deploy improvements with far greater confidence. It creates an environment where innovation becomes part of the day-to-day development process, rather than something that only happens during major platform upgrades.
You’ve spoken about giving operators greater control of their technology and data. Have too many businesses become locked into closed platform ecosystems?
Closed platforms have played an important role in helping many operators launch and grow, but businesses naturally become more ambitious over time. As they mature, they want greater control over their roadmap, the freedom to integrate new capabilities and more influence over how their platform evolves. That’s becoming even more important as AI accelerates software development and raises expectations around speed and innovation. It’s not a case of rejecting closed ecosystems altogether; it’s about giving operators more choice over the parts of the platform that define their business.
Much of the AI conversation focuses on player engagement. Could its biggest impact actually be in software development behind the scenes?
Everyone is talking about AI and player engagement, but the bigger story is happening behind the scenes. AI is changing how software is developed. That has implications far beyond development teams because if you can shorten delivery cycles and reduce engineering overhead, the business can respond more quickly to new opportunities. In the long run, AI’s greatest impact won’t be a single feature that players interact with. It will help companies innovate faster across the board.
Having worked with operators across the industry, what technical mistakes do you see businesses repeatedly making as they try to scale?
One mistake we often see is solving today’s problem without thinking about tomorrow’s challenge. That’s understandable when there’s pressure to launch quickly, but short-term decisions have a habit of becoming long-term constraints. Over time, platforms become more difficult to change, integrations take longer and development slows just when the business needs to move faster. The companies that scale most successfully aren’t necessarily those with the biggest engineering teams; they’re the ones that continue investing in platform design, so growth doesn’t come at the expense of agility.
How can modern platform architecture make it easier for operators to meet regulatory requirements and expand into new markets?
Expanding into a new market is rarely just about obtaining a licence. It’s about adapting your platform to different regulatory, operational and commercial requirements without creating unnecessary complexity. That’s where good architecture makes a real difference. If your platform is designed to evolve, introducing market-specific functionality or integrating local services becomes a far more manageable process. It doesn’t remove regulatory complexity, but it does stop every new requirement from becoming a major engineering project.
What will define the next generation of iGaming platforms, and where do you see AI having the greatest influence?
The industry is moving towards platforms that are built to evolve, not simply to scale. For a long time, success was measured by stability and the number of features a platform could offer. Increasingly, it will be defined by how quickly businesses can respond to change. AI will undoubtedly play a major part in that, not because it will replace engineering teams, but because it can help them solve problems faster and make better use of their expertise. The businesses that adapt first will be in the strongest position to keep innovating over the next decade.
