VLT software is the system behind a floor of video lottery terminals: the client on each machine, the server that runs the games, and the back office where you see what every terminal took last night. This is the platform we license to operators running shops, arcades and gaming halls. It is server-based, so the machine on the floor does very little work — the minimum terminal we support is a dual-core i3 with 4 GB of RAM and integrated graphics.
What VLT software actually has to do
Before comparing platforms, it helps to be specific about the job. A terminal floor is eight separate problems that happen to share a cabinet. Most of what gets sold as “VLT software” covers four or five of them and leaves you to solve the rest with spreadsheets and phone calls.
Run the machine
The client the player touches: lobby, sessions, what happens when the connection drops, and keeping Windows out of reach.
See the floor
Which terminals are up, what each one holds, who is on shift, and last night's numbers without walking the room.
Supply the content
Enough games that regulars do not get bored, connected once rather than integrated one studio at a time.
Move the money
Cash in through the validator, cash out at the desk, and a record that reconciles at the end of the day.
Give them a reason to stay
Jackpots linked across a venue or a whole estate, with the contribution maths you can show a regulator.
How our video lottery terminal software is built
The platform is server-based and cloud-hosted. Game logic and the random number generator run centrally; the terminal renders the result and handles the peripherals in front of it. That single decision explains most of what follows on this page.
It means the machine on the floor is a thin client, so it does not need gaming hardware. It means adding a game to your library is a change on the server rather than a visit to twenty cabinets with a USB stick. It means the numbers you read in the morning came from the same place the games ran, so there is nothing to reconcile between the machine and the report.
It also means an interruption is survivable. If a terminal loses its connection or its power mid-session, the session and its state are restored when it comes back — the server was holding them the whole time, not the machine.
The architecture is covered in more depth on server-based gaming.
The admin panel — what you control from one screen
One back office covers every venue you run. Terminals, players, cash, sessions and RTP are all in the same place, so a multi-venue operator is not logging into a system per site or waiting for a manager to send numbers.
The structure is a hierarchy. An operator account holds venues, a venue holds terminals, a terminal holds sessions, and a session is the record every number on every report eventually traces back to. Permissions follow the same shape, so a venue manager sees their room and a head office sees all of them.
The practical test of a back office is whether you can answer a question without walking the floor or phoning a manager. Which machine is down. What the room took last night. Whether that payout matches the shift. Those are the questions the panel is built around.
The reporting and monitoring side has its own page: the terminal management system.
Game content connected out of the box
Content is the difference between a floor that holds its regulars and one that empties out by month three. Terminals draw on the same aggregated library as our online platform: more than 25,000 titles from over 150 studios, reached through a single integration, covering slots, table games, crash and instant titles, jackpot content, and the fishing and arcade categories most aggregators skip.
Because games run server-side, your library is a configuration rather than a deployment. Studios and individual titles are switched on and off per operator in the dashboard, so a venue in one market can run a different floor to a venue in another without anyone touching either machine. New releases from a studio you have enabled appear automatically, according to rules you set.
The full picture is on games for gaming terminals.
Bonuses, jackpots and player retention
A terminal player is anonymous unless you give them a reason not to be. That is the whole retention problem in land-based gaming, and it is why the bonus and jackpot layers matter more here than they do online.
Jackpots run in two shapes. Linked in-venue pools connect the machines under one roof, so a room of six terminals can advertise a prize no single cabinet could fund. Wide-area progressives link venues across your whole estate into one pool, which is how a small operator gets a headline number on the wall.
On the bonus side: promocodes, happy hours, wager-based rewards, wheel of fortune and free spins. All of it is issued and tracked from the same back office as the rest of the platform, so a cashier handing out an incentive on a quiet Tuesday is not working from a paper list.
Detail on the jackpot system and bonuses for terminals.
Cash in, cash out
This is the part operators ask about first and vendors describe last. Money enters through a bill validator and leaves over the counter, and every step has to land in a record that still balances at the end of a shift.
The platform speaks ccTalk, SSP and ID003, which covers the bill validator families most operators already own — ITL, JCM, ICT and Cashcode units all communicate over one of those three. Ticket printing uses ESC/POS, so standard thermal printers work rather than a proprietary model you have to source from us.
Be clear about what the standard platform does today: cash in through the validator, payout through the cashier. Ticket-in ticket-out, coin hoppers and card readers for player accounts are not part of the shipping product. If your market or your venue format requires any of them, they are development we scope and quote for your deployment rather than a switch we turn on. Raise it early, because it changes both the timeline and the hardware list.
The hardware question — you don’t need to buy cabinets
Most VLT vendors quote you cabinets. That is where the cost sits, and it is usually the reason a small operator never starts. Our client runs on ordinary PC hardware, because the server is doing the work.
| 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 |
Read the graphics row again: integrated Intel HD meets the minimum. No discrete card, which means office-grade mini PCs and thin clients qualify. If a machine can run a spreadsheet, it can run a terminal. An operator with ten ageing office PCs in a back room has ten terminals waiting.
Worth knowing before you commit to the floor of the range. Machines at the minimum spec often need Visual C++ redistributables and Mesa 3D installed by hand to render properly. At the recommended spec they do not. The minimum is genuinely supported — it is also more setup work and more support calls, and across twenty terminals that difference is a working week.
The 200 ms latency figure deserves the same attention. Many server-based platforms start to degrade around 120 ms. Two hundred covers mobile broadband and venues with no fixed line, which is the objection that usually ends the conversation in secondary cities and rural markets. Bandwidth we size per deployment, since a room of twenty machines is a different question to a shop with three.
One note on the operating system. Windows 10 is the minimum we support, but it stopped receiving free security updates in October 2025. These machines handle cash and sit unattended in public venues, and certification labs expect a patched OS, so Windows 11 is what we recommend for anything being built now. Existing Windows 10 estates keep working.
Deployment: from contract to first spin
Five steps, in this order.
- Scoping. Market, venue count, terminal count, game mix, and what hardware you already have. This is where anything non-standard — TITO, a hopper, a card reader — has to surface, because it changes everything after it.
- Agreement and licensing check. Commercial terms, and confirming we can supply your jurisdiction.
- Server provisioning and back-office setup. Your cloud instance, with venues, users, permissions and the game library configured for your market.
- Terminal imaging. Client install, kiosk lockdown, peripheral configuration for your validators and printers, and IP whitelisting.
- Installation and go-live. Machines placed and tested in the venue, cashier and floor staff walked through the back office, then live with support through the first weeks.
Three to five days end to end, assuming the hardware is on site and nothing in the scoping step turns out to be non-standard.
Operators who would rather not assemble any of it themselves should look at the turnkey gaming hall.
Integrations and protocols
The platform speaks SAS for gaming machine reporting and accounting, ccTalk, SSP and ID003 for note acceptance, and ESC/POS for ticket and receipt printing.
Hosting is cloud-side, so there is no server for you to buy, rack or patch. Terminals reach it over an IP whitelist — no VPN client to install on every machine, and no tunnel to keep alive in a venue with a consumer router. Your IT contact needs to supply the venue’s public address, and that is roughly the extent of the network work.
Full list on integrations and protocols.
Markets we supply
We do not supply operators in Romania, Malta, Latvia, the Isle of Man, Gibraltar, Curaçao or Bulgaria. If you operate in one of those jurisdictions we are not the right supplier, and saying so here saves us both a call.
See certification and compliance.
VLT software providers compared
If you are shortlisting, you should be reading more than one vendor’s own page. We keep an honest comparison of the platforms in this market, including where each of them is a better fit than we are.
Questions operators ask
What hardware do I need to run your VLT software?
At minimum, a dual-core Intel Core i3 at 2.80 GHz, 4 GB of RAM, 64 GB of storage, graphics with 1024 MB of video memory, and Wi-Fi or LAN with latency of 200 ms or better. Integrated Intel HD graphics qualify. We recommend an i5-6000 series or Ryzen 5 2000-series processor or newer, 8 to 16 GB of DDR4 and a 120 GB SSD, which avoids the manual driver work minimum-spec machines need.
Can I use PCs I already own instead of buying cabinets?
If they meet the minimum specification, yes. Because game logic and the random number generator run on the server, the terminal only renders the result and drives its peripherals. Retrofitting existing machines is a normal way to start rather than a compromise, and it removes the largest single cost from opening a venue.
Will it work in a venue with a poor internet connection?
The platform tolerates latency up to 200 ms, which covers mobile broadband and venues without a fixed line. Many server-based systems begin degrading closer to 120 ms. Bandwidth is sized per deployment, since twenty terminals in a hall is a different requirement to three in a shop.
What happens to a session if a terminal loses power or connection?
The session is restored. State lives on the server rather than the machine, so when the terminal comes back the player continues where they were and the balance is intact. Nothing has to be reconstructed by hand or written off by a manager.
Does the platform support TITO?
Not in the standard product. Today the platform handles cash in through the bill validator and payout through the cashier. Ticket-in ticket-out, coin hoppers and player card readers are custom development, scoped and quoted per deployment. If your regulator or venue format requires TITO, raise it in the first conversation, because it affects both the schedule and the hardware you buy.
Which bill validators and printers work?
Anything speaking ccTalk, SSP or ID003, which covers the ITL, JCM, ICT and Cashcode families most operators already have installed. Printing is ESC/POS, so standard thermal printers work and you are not tied to a single model.
What does it cost?
Two models: revenue share, or a fixed monthly licence per terminal. Which suits you depends on how many machines you run and how confident you are in the floor’s take — revenue share carries less risk on a new venue, a per-terminal licence works out cheaper once the floor performs. We will talk through both against your numbers.
See it on your own hardware
Bring your terminal specification and your market. We walk through the back office and the client against what you actually have, rather than a prepared deck.