Hero Nexus · The edge layer

The software that runs the machine.

Hero Nexus is the Android edge application inside the payment terminal. It takes payment, drives the machine over MDB, Executive, VMC and PLC, and reports telemetry — offline-first, secure, and updated over the air.

Talk to engineering See the cloud layer
Android edge Offline-first OTA updates
An Hero Nexus core at the centre of the terminal connects to six interfaces — payment, MDB, Executive, vend control, PLC and sensors — and down to a local database, a secure uplink to QuadC and OTA updates. Payment terminal Payment EMV · NFC MDB peripherals MDB Executive EXECUTIVE Vend control VMC PLC machines MODBUS Sensors TELEMETRY Hero Nexus Android edge software Local database → QuadC OTA
  • EMV
  • MDB
  • EXECUTIVE
  • MODBUS
  • VMC
  • OTA

What Hero Nexus controls

One application, every interface on the machine

The same edge software speaks to the payment stack, the vending controller and the industrial PLC — so one integration covers the whole machine, whatever it dispenses.

Payment Card, contactless, QR and meal cards through the terminal's certified EMV and NFC stack.
MDB Acts as a cashless device on the MDB bus for vending machines and peripherals.
Executive Speaks the Executive protocol for older machines that never spoke MDB.
VMC Drives the vending machine controller directly — selection, vend and change logic.
PLC · Modbus Maps start and vend signals to PLC-controlled machines over Modbus.
Telemetry Reads sales, stock, temperature, errors and uptime, and streams them to the cloud.

Offline-first

The machine keeps selling when the network drops

Hero Nexus holds a local database on the device. Payments authorize, vends complete and telemetry is recorded whether or not the connection is up — then everything reconciles to QuadC the moment it returns.

  • Local database on the device

    Transactions, configuration and telemetry persist on the terminal, not only in the cloud.

  • Buffer and reconcile

    Events queue while offline and sync in order when the link is back — nothing is lost, nothing is double-counted.

  • Deterministic at the edge

    Vend logic runs locally, so latency and outages never leave a customer waiting on the cloud.

18:04:11 VEND OK · ₺45,00 QUEUED
18:04:39 VEND OK · ₺12,50 QUEUED
18:05:02 TEMP 4.2°C QUEUED
18:05:12 LINK UP · SYNC → QuadC OK

Built for the field

Secure by design, updated over the air

The terminal lives unattended for years. Hero Nexus is built for that: encrypted where it matters, and updatable without a site visit.

Secure communication

  • Encrypted uplink

    Device-to-cloud traffic runs over TLS; payment follows the terminal's certified secure path.

  • Authenticated devices

    Each terminal is identified to QuadC, so a fleet is a set of known, addressable devices.

  • Least privilege

    The edge holds only what it needs; sensitive operations stay inside the certified payment stack.

OTA updates

  • Update without a visit

    Software, configuration and content ship to the terminal over the air from QuadC.

  • Staged and reversible

    Roll out by group, watch telemetry, widen — or roll back a bad build.

  • Version-aware fleet

    Every device reports its build, so you always know what is running where.

See where the edge data goes

Hero Nexus streams to QuadC, the cloud layer that turns a device into a fleet. Follow the data up a layer.

Explore QuadC Talk to engineering