VAYAOS / PURPOSE-BUILT RETAIL COMPUTING

A register.
Engineered as
an appliance.

A controlled Linux environment. A local checkout engine. A hardware stack built around HP Engage. Every layer has a job to do when the line gets long.

Developed in New York.
Shaped by high-pressure retail environments.
PLATFORM / HP ENGAGE01—ESSENTIAL
HP Engage One Essential all-in-one retail system, manufacturer product image
HP Engage One EssentialLOCAL-FIRST
LINUX APPLIANCE

HP product image with manufacturer’s sample interface. See the actual Vaya POS.

01 / EXECUTIONLocal Node.js
02 / CHECKOUT DATASQLite per register
03 / STORE SYNCPostgreSQL
04 / HARDWAREHP Engage

THE OPERATING PHILOSOPHY

The whole system.
Accounted for.

A busy checkout lane exposes the gaps between an application, its operating system, and its peripherals. VayaOS brings those layers into one controlled retail environment.

Boot behavior, cashier access, local data, scanner input, scale responses, terminal communication, and receipt output are part of the same engineering problem. The operating system becomes a managed part of the product, with maintenance planned around the store.

Read the appliance design

01 / A LOCAL PATH TO THE SALE

The internet is not
in the scan path.

A barcode resolves against the register’s local catalog. Store synchronization runs separately. A network interruption changes what can synchronize; it should not turn a working register into a waiting screen.

Understand the failure boundaries
Store topologySQLite → asynchronous sync → PostgreSQL
External servicesInternet / processor networkExternal services available
R01Store Hub + Register

Checkout stays local.

LOCALSQLiteCatalog · checkout · recent history
STOREPostgreSQLSynchronization · shared archive
LAN SYNC
R02+Additional Register

Its own checkout engine.

LOCALSQLiteCatalog · checkout · recent history
Local device adaptersScanner / scale / printer / terminal

Conceptual deployment topology. Each lane requires power and its own functioning local services.

Offline checkout and payment authorization are different capabilities. Card and EBT authorization depend on the terminal, processor, and available connectivity.

THE TECHNICAL LIBRARY

Go below
the interface.

For the people who need to understand what happens after a scan, during a network failure, and behind the end-of-day total.

THE OPERATOR’S VIEW

Built for the work
in front of you.

Touch targets, quick categories, tender controls, and searchable ticket history. The interface reflects the job at the counter.

Explore actual POS screens
Checkout / ready for the next saleVAYA WERK POS
Checkout / ready for the next saleInspect screen
The actual cashier workspace, with product-image shortcuts, numeric entry, and cash / card controls.
AN APPLIANCE IS AN ENGINEERING COMMITMENT.

Every layer matters.
Especially under pressure.

Start with the architecture