The software platform behind smart self-service machines
Engineering the Future of Self-Service.
Hardware-independent software for self-service machines: Android edge devices, cloud telemetry, integrated payment and browser-based fleet operations — built on 30 years of embedded engineering.
Just need card and contactless payment on your machine? That's the simplest thing we do — MDB, PLC, coin-op or mechanical, it can be fitted to any of them.
Get a quick answer
How would you like us to answer?
WhatsApp Write to us now — usually answered the same day. E-mail Send the form — we reply within one business day.- MDB
- PULSE
- MODBUS
- OTA
- API
Payment
Four payment worlds, one integration
Taking money is one of the jobs our terminals do every day — cards, meal vouchers, transit cards and wallets, on the same board and the same integration. You certify once; the platform handles the rest.
-
Card networks
Contactless, chip and magstripe
-
-
Meal cards
Turkey's meal-voucher ecosystem
-
-
Transit cards
City transit stored value
-
-
Closed-loop credit
Corporate CSC and campus wallets
- CSC
-
30 years
Three decades of self-service engineering
From R&D in 1996 and the first prototypes in 1998, to the first vending card payment shipped in 1999 — through Akbil closed-loop, contactless and meal cards — to a full Android edge and cloud platform. The payment problem taught us the machines; the machines became the platform.
Industries
If it serves, dispenses or starts on demand, it runs on DMS
One platform across a dozen self-service categories — and any PLC-controlled machine behind them.
The platform
Three layers, one ecosystem
Hero Nexus on the machine, QuadC in the cloud, HERO in the browser — connected by one secure real-time link. Each layer does one job well; together they run the fleet.
Hardware-agnostic
One platform. Unlimited hardware.
Terminal hardware changes; the platform stays constant. Hero Nexus runs on Nexgo today and is built to run on PAX, SUNMI, Castles and Newland next — no redesign, no re-integration.
-
Swap the terminal, keep the platform
Move to new hardware without rebuilding integrations or retraining operators.
-
No vendor lock-in
Payment, telemetry and fleet logic live in the platform layer, not the device.
-
One skill set, every terminal
The same Hero Nexus software, MDB handling and cloud apply across each supported brand.
Smart VMC
Modernize the machine you already own
Turn a keypad-and-LED vending machine into an Android, cloud-connected, card-accepting machine — without replacing it. One investment; the machine stays.
LED display + keypad
Coins and notes only. No card acceptance, no telemetry, no remote control, no data.
Android touchscreen
Card, QR and meal-card payment, cloud telemetry and OTA updates — on the very same machine.
The mechanics stay; the electronics and software become current. One machine, upgraded — not replaced.
See Smart VMCPLC & Modbus
Payment for machines never built to take it
We integrate payment directly into PLC-controlled machines over Modbus — car washes, arcades, massage chairs and custom industrial automation. Written as an engineering note: problem, protocol, result.
Problem
The machine is controlled by a PLC with no payment interface and no path to modern cashless acceptance.
Protocol
Hero Nexus speaks Modbus to the PLC, mapping start and vend signals to real-time payment authorization.
Result
The machine now takes cards, QR and meal cards and reports telemetry — with no mechanical redesign.
- Car wash
- Arcade
- Massage chairs
- Industrial automation
- Custom machines
Engineering notes
What we write about, we have shipped
Protocols, telemetry, payment and the build-vs-buy questions operators and machine makers actually ask — written in the language of engineering, not sales.
- Comparing vending payment and telemetry suppliers: the ten rows that decide it Put three quotes side by side and the brochures say the same thing: every card scheme, every machine, real-time dashboard, 24/7 support. What actually separates suppliers never reaches the quote — who holds the acquirer relationship, where telemetry originates, who owns the data, and what leaving costs. Ten dimensions, and how to verify each one before you sign. Read the post
- MDB compliant, still not talking: the failure modes you actually meet The machine doesn't see the cashless device. The reader works on one model and not another. It fails only during a transaction. Here is what actually causes MDB interoperability failures, and the order to diagnose them in. Read the post
- Vending management system or platform? The difference is scope A VMS is a set of management functions; a platform is the stack that produces the data underneath it. Why fleets assembled from several vendors stop reconciling, what free telemetry actually costs when a chargeback or an audit arrives, how mixed-brand machines end up in one data model — and ten questions to ask before you sign. Read the post
Talk to the engineers behind the platform
Tell us about your machines and your fleet. We'll show you how Hero Nexus, QuadC and HERO fit — on the hardware you already run.