The platform

One platform. Three layers. Any machine.

Hero Nexus runs on the machine, QuadC runs the cloud, HERO runs in the browser — one ecosystem, connected by a single secure real-time link. Built on 25 years of embedded engineering and independent of the terminal underneath.

Talk to engineering Start with the edge layer
Secure real-time link OTA built in Open API
The Live Wire Live data path: a machine reports through Hero Nexus on the device, QuadC in the cloud and HERO in the browser, to the operator. MACHINE Vending · coffee · car wash Hero Nexus Android edge software QuadC Cloud platform HERO Browser operations OPERATOR Any device, anywhere VEND OK · ₺45,00 TEMP 4.2°C OTA 100% STOCK 12
  • MDB
  • EXECUTIVE
  • MODBUS
  • OTA
  • REST API

Three layers

Each layer does one job well

The machine reports through Hero Nexus on the device, into QuadC in the cloud, out to HERO in the browser. One path, three layers — click into any of them.

Hero Nexus · Edge Android software on the machine Runs inside the payment terminal: payment, MDB, Executive, VMC and PLC control, telemetry — offline-first with a local database and OTA updates. Explore Hero Nexus QuadC · Cloud The platform that runs the fleet Device management, telemetry ingestion, users and authorization, reports and analytics, OTA distribution, notifications and an open API — multi-tenant by design. Explore QuadC HERO · Browser Operations, with nothing to install Live fleet status, sales and revenue, alarms, reports with Excel and PDF export, and remote configuration — on any device, in the browser. Explore HERO

The three layers are joined by one secure real-time link. The machine stays connected when the network drops and reconciles the moment it returns.

  • TRANSPORT TLS-encrypted
  • LATENCY Real-time
  • OFFLINE Local buffer, auto-reconcile

Hardware-agnostic

One platform. Unlimited hardware.

The terminal is a detail, not the product. Hero Nexus runs on Nexgo today and is built for PAX, SUNMI, Castles and Newland next — the platform layer stays constant beneath whichever device you deploy.

  • Swap the terminal, keep the platform

    Move to new hardware without rebuilding a single integration or retraining an operator.

  • No vendor lock-in

    Payment, telemetry and fleet logic live in the platform, not the device.

  • One skill set, every terminal

    The same Hero Nexus software, protocol handling and cloud apply across every supported brand.

OTA & open API

Update the fleet and build on top of it

The platform is open at both ends: push software to every machine over the air, and read or write the same data your operators see through a documented REST API.

Over-the-air updates

  • Ship to the whole fleet

    Push a new Hero Nexus build to one machine or ten thousand from QuadC — no site visit.

  • Staged rollout

    Release by group, watch the result, then widen. Roll back if a build misbehaves.

  • No truck rolls

    Firmware, configuration and content update remotely, so field trips stay rare.

Open REST API

  • Devices, transactions, telemetry

    Read fleet state and history over a documented REST API, authenticated per tenant.

  • Webhooks

    Subscribe to sales, alarms and status changes and push them into your own systems.

  • Build your own surface

    ERP, accounting or a custom dashboard — HERO is one client of the API, not the only one.

See the platform on your machines

Tell us what you run today. We'll show you how Hero Nexus, QuadC and HERO fit — on the hardware already in the field.

Talk to engineering Explore Hero Nexus