Engineering · Since 1999

Engineering first. For twenty-five years.

We did not start as a platform company. We started by making a vending machine take a card in 1999 — and kept solving the next hard problem, from custom boards and protocols to Android and cloud. The platform is what that engineering became.

25+ years of engineering
1999 first card payment on a machine
3 layers: edge · cloud · browser

Engineering First

The problem, then the product

Every layer of the platform exists because a real machine needed it. We are engineers before we are a vendor: we would rather understand your machine down to its control board than sell you a box and leave. That bias shows up in everything we ship.

  • We own the whole stack

    From the board and the protocol on the machine to the cloud and the browser — one team, one mental model, no integration seams to hide behind.

  • Depth over breadth

    We would rather do payment, telemetry and control properly on one platform than shallowly across ten. The focus is why it holds up in the field.

  • Built to last a hardware generation

    Terminals change every few years; our software is designed so the platform outlives the device under it. Hardware changes — the platform remains.

How we got here

From embedded systems to cloud platforms

The same team followed the problem up the stack. Each step below was a real capability we had to build before the next one was possible — this is the path, not a marketing arc.

  1. Embedded Embedded systems The starting craft: firmware and real-time control on constrained hardware, where a dropped byte is a failed sale.
  2. Boards Custom electronics When off-the-shelf boards couldn't do the job, we designed our own — payment and control electronics built for the machine.
  3. Protocols MDB & Executive Speaking the machine's own language: MDB and Executive to the VMC, so the terminal controls the vend, not just the payment.
  4. Payment Payment electronics Two decades of acceptance — online cards, contactless, closed-loop, meal cards, QR — engineered into the machine, not bolted on.
  5. Android Android edge Hero Nexus: the control and payment logic moved onto Android at the edge, offline-first, updatable over the air.
  6. Cloud Cloud & browser QuadC and HERO: telemetry, fleet management and operations in the cloud and the browser, on top of everything below.

What we know deeply

The disciplines behind the platform

These are not buzzwords on a slide — they are the areas we have shipped in production for years. Any one of them is a conversation you can have with our engineers in detail.

Embedded & firmware Real-time control on constrained hardware, where reliability is measured in years of unattended operation.
Custom boards In-house payment and control electronics designed for the machine, not adapted from something else.
Machine protocols MDB, Executive and Modbus — VMC and PLC control, so the platform runs the machine, not just the till.
Payment electronics 25 years of card, contactless, closed-loop, meal-card and QR acceptance, engineered into the device.
Android edge Offline-first edge software with a local database and OTA — the machine keeps working when the network doesn't.
Cloud & OTA Multi-tenant telemetry ingestion, fleet management and over-the-air distribution at fleet scale.

25 years

A quarter century, in milestones

The same story on a rail: the payment problem taught us the machines; the machines became the platform.

1999
First online card payment on a vending machine, on Yapı Kredi infrastructure.
2008
Contactless credit and debit acceptance, via Garanti.
2015
Meal cards — Edenred, Multinet, Setcard, Metropol, Sodexo — and İstanbulkart.
2020
QR payments across the fleet.
2026
The Hero Nexus · QuadC · HERO platform: edge, cloud and browser operations.

Talk to the engineers, not a sales desk

Bring us a hard machine, an old estate or an integration nobody else will touch. That's the conversation we like having.