Running gaming machines in a physical venue needs more software than people expect. Something on the terminal. Something that decides outcomes. Something that tracks money. Something that controls who can change what. And something that tells you, on a Monday, whether last week worked.
This page is the map: what each part of the stack does, and where to read about it in detail. If you already know you are shopping for a terminal platform, the VLT software page is the deeper read.
The parts
The terminal client
Runs on the machine, renders games, drives the note acceptor and printer. Locked down and deliberately undemanding — a dual-core i3 with 4 GB of RAM is enough.
The back office
A multi-level agent tree covering dealers, agents, halls, cashiers and terminals, with balances, permissions and reporting following the structure.
The content
More than 25,000 titles from over 150 studios through one integration: slots, fish, roulette, keno, instant win and table games.
The retention layer
Six jackpot levels pooled by hall or by agent, plus promocodes, happy hours, free spins and wheel of fortune.
The money layer
Note acceptance over ccTalk, SSP and ID003, ESC/POS ticket printing, and cash desk control.
Those six are one system rather than six products bolted together, which is the practical difference from assembling a floor out of separate vendors. A spin is recorded once, and the same record is what the jackpot draws on, what the report counts and what the cashier reconciles against.
Which venue are you running?
The stack is the same in every case. What changes is how much of it you switch on.
| Venue | Terminals | What matters most |
|---|---|---|
| Shop or bar corner | 2–4 | Small footprint, cheap hardware, fast rounds. Reliability matters more than bonuses |
| Arcade or game room | 8–15 | Game mix and dwell time. Bonuses start paying for themselves |
| Gaming hall | 20 or more | Jackpots, loyalty, staff permissions, shift reconciliation |
| Internet café | Varies | Low cost per seat, casual content, existing PCs |
| Distribution network | Many halls | The agent tree. This is the one other platforms handle badly |
That last row is worth dwelling on, because it is where most land-based casino software quietly assumes something untrue about your business. Nearly all of it is built around one operator running their own venues.
If you place terminals through agents who run their own halls, you need a platform where each level funds, manages and sees only its own branch — and where you can delegate the work of running a room without handing over a balance to go with it. That is a structural property, not a settings page, and it is the hardest thing to retrofit once you have chosen wrong.
Online and land-based on the same content
We also run an online platform, and both sides draw on the same aggregated game library through the same integration layer. For an operator running a website and a floor of terminals, that means one content relationship rather than two — the same studios, enabled the same way, reported in the same formats.
The online side has its own overview on casino software solutions.
What it runs on
| Component | Minimum | Recommended |
|---|---|---|
| Operating system | Windows 10, 64-bit | Windows 11, 64-bit |
| Processor | Dual-core Intel Core i3, 2.80 GHz | Intel Core i5-6000 series or newer, or AMD Ryzen 5 2000–3000 series or newer |
| RAM | 4 GB | 8–16 GB DDR4 |
| Storage | 64 GB | 120 GB SSD |
| Graphics | GeForce, Radeon or Intel HD — 1024 MB video memory | Same, on a current driver |
| Network | Wi-Fi or LAN, latency 200 ms or lower | Wired LAN |
Office hardware, in other words. The server side is cloud-hosted, so there is nothing to rack in the venue and nothing to patch — terminals reach it over an IP whitelist, with no VPN client to maintain on every machine.
Getting started
Licensing is revenue share or a fixed monthly fee per terminal. Deployment runs three to five days end to end once the hardware is on site and nothing in scoping turns out to be non-standard.
We supply licensed operators in most markets, excluding Romania, Malta, Latvia, the Isle of Man, Gibraltar, Curaçao and Bulgaria.
Questions operators ask
What is land-based casino software?
The software running gaming machines in a physical venue: the client on the terminal, the server deciding outcomes, and the back office controlling money, permissions and reporting. It is usually sold as one system rather than three, because the three have to agree with each other about every transaction.
Do I need a server in my venue?
No. The platform is cloud-hosted. A venue needs a connection, not a server room — and the connection can be Wi-Fi or mobile broadband, since the client tolerates latency up to 200 ms.
Can I run it on ordinary PCs?
Yes, and that is the design rather than a concession. Minimum specification is a dual-core i3 with 4 GB of RAM and integrated Intel HD graphics, because game logic runs on the server and the terminal only renders the result.
Can I run several halls under different managers?
Yes. The user structure is a multi-level agent tree where each level sees and funds only its own branch, and sub-roles exist so a technician or cashier can do their job without holding a separate balance.
Is the game library the same as your online platform?
Yes — both sides draw on the same aggregated library through the same integration layer, so an operator running both maintains one content relationship instead of two.
Which markets do you not supply?
Romania, Malta, Latvia, the Isle of Man, Gibraltar, Curaçao and Bulgaria. If your market is not on that list, we can almost certainly supply it, and the practical question becomes your licence rather than our reach.
Not sure which part you need?
Describe the venue — how many machines, who runs them, which market. We will tell you what the stack looks like for that shape of operation, including the parts you do not need yet.