Most gaming terminal software is sold with the cabinet. You buy the machine, you get the software, and the price of one decides the price of the other. That works until you want twenty terminals and the quote comes back at a number that only makes sense inside a casino.
Our client runs on a standard Windows PC. Intel HD graphics is enough. Four gigabytes of RAM is enough. If a machine can run an office suite, it can run a gaming terminal — which turns the hardware question into a sourcing decision instead of a capital event.
That is the whole idea behind our VLT software: game logic and the random number generator sit on our servers, and the terminal renders, takes money and reports. It does not need to be powerful, because it is not doing the hard part.
What runs on the machine
The terminal client is a locked-down application, not a browser pointed at a website. It boots into the game lobby, holds the session, drives the cash peripherals, and talks to the central server over the venue’s existing connection.
Session integrity
The failure every operator has lived through is a machine dropping mid-spin with credit on it. The player is angry, the cashier has no record, and somebody is guessing at a refund.
The session is held server-side and fully restored after power loss or connection loss. A terminal that loses power mid-game comes back to the same session, the same balance and the same state. Nothing is rebuilt from the machine’s local storage, because nothing important was ever stored there.
Connection tolerance
The client is built to survive bad connectivity rather than to assume good connectivity. It runs over Wi-Fi or wired LAN at up to 200 ms latency — a threshold that matters in venues where the connection is a mobile router on a shared cell, not a leased line. Many server-based platforms start degrading closer to 120 ms.
Bandwidth we size per deployment. A shop with three machines and a hall with twenty are different questions, and a single number quoted for both would be no use to either.
What the operator controls remotely
Nothing that changes a terminal’s behaviour requires a visit to the venue. Game mix, denominations, limits and language are set per machine or per venue and pushed from the back office.
Hardware requirements in plain numbers
| 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 |
Two caveats worth stating plainly rather than burying. Machines at minimum spec usually need the Visual C++ redistributable and Mesa 3D installed by hand before first run — a one-time step per machine, but a step, and across twenty terminals it adds up to a working week. At the recommended spec they do not.
The second: Windows 10 stopped receiving free security updates in October 2025. These machines handle cash and sit unattended in public venues, so anything being built now should go out on Windows 11. Existing Windows 10 estates keep working.
Cash handling and peripherals
The client speaks ccTalk, SSP and ID003 for note acceptance and prints over ESC/POS. Those three protocols cover the bill validators in general circulation, which makes peripheral sourcing a purchasing decision rather than a compatibility gamble. The validator that is cheap and serviceable in Lagos is not the one that is cheap and serviceable in Lima, and you should be free to buy either.
Ticket-in ticket-out, coin hoppers and card readers are custom development on request rather than standard product. If your venue format needs them, they are built to specification and quoted separately. Better said here than discovered during integration.
Game content
The client connects to a library of more than 25,000 titles from over 150 studios — slots, roulette, keno, video poker, fish games and table formats. Adding a studio is a configuration change in the back office, not a redeployment and not a site visit.
Server model and connectivity
The platform is cloud-hosted, so there is no server for you to buy, rack or patch. Terminals reach it over an IP whitelist — no VPN client to maintain on every machine, and no tunnel to break at three in the morning. You supply the venue’s outbound address and that is the network work done.
Where we operate
We supply licensed operators in most markets, with exclusions. We do not supply Romania, Malta, Latvia, the Isle of Man, Gibraltar, Curaçao or Bulgaria.
Listing the exclusions rather than claiming global coverage saves us both a call. If your market is not on that list we can almost certainly work there, and the practical question becomes your licence rather than our reach.
Commercial model
Two options: revenue share, or a fixed monthly licence per terminal. Which works better depends on your venue’s turnover and how much risk you want on your side of the table. Revenue share carries less exposure on a new room; a per-terminal licence works out cheaper once the floor performs. We will tell you which suits your numbers, including when that is the cheaper one for us to sell you.
Questions operators ask
Can I run this on PCs I already have?
If they meet the minimum specification — dual-core i3 at 2.80 GHz, 4 GB of RAM, 64 GB of storage and 1024 MB of video memory — yes. Integrated Intel HD graphics is supported. Machines at minimum spec need the Visual C++ redistributable and Mesa 3D installed manually before first run.
What happens if a terminal loses power mid-game?
The session is held on the server, not the machine. When the terminal comes back up the player returns to the same session with the same balance and the same game state. No manual reconciliation, no guessing at a refund.
Do I need a VPN between my venue and your servers?
No. The platform is cloud-hosted and access is controlled by IP whitelist. You give us the venue’s outbound address and that is the connection set up.
Which bill validators are supported?
Any validator speaking ccTalk, SSP or ID003. Ticket printing uses ESC/POS, so standard thermal printers work. Coin hoppers, card readers and TITO are custom development rather than standard product — tell us the venue format and we will quote them.
How much bandwidth does a terminal need?
We size it per deployment, because the answer depends on how many machines share the connection and what else is running on it. Latency is the figure worth checking first: up to 200 ms works.
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.
Related
VLT software
The platform this client belongs to: server, games, back office and terminal together.
Terminal management system
The control layer: monitoring, remote configuration and reporting across every venue.
Games for gaming terminals
Categories, studios and how to build a game mix by venue type.
TITO and cashless
How money moves through a terminal, and what ships as standard.
Run it on a machine you already own
Send us the specification of a PC you already have and we will tell you whether it will run a terminal, before anyone talks about contracts.