Why we build a casino platform from Serbia
Published
Hassan Naveed, founder and chief executive of Scalara Labs, on what a Serbian engineering base is good for, what the work on a regulated platform actually demands, and how a small team runs it across three time zones.
When people ask where Scalara is built, the answer surprises some of them. The commercial side of the business sits in the United Kingdom, the United Arab Emirates and Europe. The engineering base is in Serbia. That was a deliberate choice, and having built a regulated casino platform there, I think the reasons are worth setting out, because they say as much about the work as they do about the place.
The talent was already there
Serbia did not need an iGaming company to discover its engineers. The government's Office for Information Technologies and eGovernment reported in February that ICT services exports reached €4.552 billion in 2025, 10% more than in 2024, with a surplus of €3.529 billion. Those are not figures produced by a few outsourcing shops. They describe a country whose engineers already build software for banks, payment companies, telecoms operators and product businesses abroad, and are used to working to someone else's standards.
That background matters more than iGaming experience. When we wrote our first senior engineering role, we said plainly that experience in gambling was not required. Several of the best engineers on the team came from other regulated industries. The domain can be learned in a few months. The judgement that comes from building systems where a mistake costs real money and attracts a regulator's attention takes years, and Serbia has a large pool of people who already have it.
What the work actually is
From the outside, a casino platform looks like a lobby full of games. Underneath, most of the engineering is about correctness under concurrency. A bet has to settle exactly once, even when a game provider's connection drops and retries the same request. A withdrawal must never be paid twice. A ledger that disagrees with itself is an incident, not a bug to be scheduled for next sprint.
We organise the team around domains rather than ticket queues. The three that need the most care are the wallet and ledger, where real, bonus and locked balances are held apart across fiat and crypto rails; the compliance engine, where a five-tier trust model decides what a player may deposit or withdraw before any money moves; and the provisioning pipeline, which takes an operator from application to a deployed environment without a person in the middle. Each domain has an owner who is expected to know it well enough that the rest of the team asks before changing anything inside it.
This is also why we hire for habits rather than frameworks. We look for people who reach for a database constraint before writing a check in application code, who treat idempotency and retries as everyday concerns, and who write a short design note before they write code. Those habits transfer from a payments company or a bank almost unchanged.
One codebase, which raises the stakes
The decision that shapes the engineering more than any other is that every deployment of our casino platform runs the same codebase. Our own brands and every private copy we deliver to a licensed operator are built from identical software. There are no customer forks.
That has a clear benefit: a fix is built once and reaches everyone, so quality compounds instead of fragmenting across branches nobody fully owns. It also has a cost the team feels every day. A change reaches everyone, and so does a mistake. You cannot ship something carelessly to one customer and tidy it up later, because there is no "one customer" version. In practice that pushes the team towards smaller changes, written review and watching what you shipped in production afterwards. Engineers coming from regulated industries usually recognise the discipline immediately.
How a small team works across three time zones
Serbia sits on Central European Time, the same as Malta and an hour ahead of London, which removes most of the friction people expect from a distributed company. The Gulf is two or three hours ahead depending on the season. Our working model assumes distance anyway, because it makes the decisions better.
We work asynchronously by default and meet deliberately: a short daily written update, one working session a week per domain, and a week together in person every quarter. Most decisions are made in writing. That is partly practical, and partly because a written argument is easier to review, easier to hand over and much easier to show a regulator or an auditor later. It is also why we ask for English good enough to argue precisely in writing, rather than for any particular accent or certificate.
We also run a real on-call rotation with handovers. Nobody is expected to be reachable at midnight as a matter of course. An always-on product needs a rota, and a team that is permanently half-awake makes worse calls on the nights that matter.
Engineers talk to operators
One thing we did on purpose was to avoid separating the people who build the platform from the people who use it. Engineers in Serbia join calls with operators in the UK, Malta and the Gulf when the subject is theirs. An operator asking why a withdrawal was held gets an answer from the person who owns the compliance engine, not a paraphrase passed through three inboxes. Engineers who hear how their work is used make different trade-offs, usually better ones.
What I would tell another company considering the region
Hire for judgement in systems that hold money, not for a gambling CV. Give people whole domains to own, because good engineers in Serbia have plenty of choice and will not stay to work through someone else's ticket queue. Put the decisions in writing. And treat the time zone as the advantage it is: close enough to Western Europe to work in real time, and far enough from the usual iGaming hubs that you are not competing with every other platform company for the same few hundred people.
The region is often described as a cost play. In our experience it is a quality play that also happens to be affordable, and the companies that treat it as the first are the ones that keep their best engineers.
About the author
Hassan Naveed is the founder and chief executive officer of Scalara Labs. He has built and scaled businesses across real estate and software in the UK, the UAE and Europe, and now leads the development of a regulated, AI native iGaming platform.