Unified devices
EOAS becomes native to the machine itself — verification, confirmation and release designed as one product, not a patchwork of add-ons.
Our roadmap extends EOAS beyond stand-alone verification into unified, EOAS-integrated devices — and into AI-embedded hardware that keeps identity, decision and release connected at scale.
The same fail-closed principles. A broader family of devices that carry them into more environments.
EOAS becomes native to the machine itself — verification, confirmation and release designed as one product, not a patchwork of add-ons.
Embedded intelligence supports capture quality, document handling and process guidance — while final accountability stays with authorised personnel.
More sites and device types, without relaxing the rule that unclear or incomplete steps never unlock a release.
Vending is the first step. More unified product lines will follow.
Today EOAS connects Terminal, StaffPad and Gateway as a controlled path. Tomorrow that path lives inside unified devices — machines where identity verification and product or play release are engineered as one system.
Our vending programme is the blueprint: self-service interaction, automated checks and a release decision that stays auditable and fail-closed. The same architecture will extend to further EOAS-integrated device families for regulated and high-trust environments.
Operators should not assemble compliance from scattered tools. They should deploy a single, coherent device that already knows how to verify, confirm and release.
Intelligence inside the hardware. Control that remains human when it matters.
We are building toward AI-embedded devices that run close to the camera, the document and the decision point — not as a black box in the cloud that overrides site responsibility.
On-device models will help keep capture sharp, guide users through the process, flag inconsistent results early and reduce friction for legitimate players. What they will not do is silently release a machine when the outcome is unclear.
Across venues and device classes, embedded AI becomes a quiet layer of precision: faster workflows, clearer signals for personnel, and stronger consistency from site to site — always under the EOAS rule that incomplete, interrupted or unconfirmed steps stay closed.
Expand the product surface. Keep the control model intact.
By 2030, EOAS should feel less like a separate verification island and more like the trust layer inside a wider family of unified and AI-embedded devices.
That is our plan: integrate EOAS into products such as vending, extend the same controlled path into new machine types, and embed AI where it improves precision — never where it weakens responsibility.