Central governance for menus, pricing, order modes, send policies, devices, releases, and operational rules.
Each application has a role. The platform stays coherent.
Nexus is designed as a connected system of applications, not a scattered set of products. Each surface exists to reinforce one operating model across governance, service, kitchen execution, deployment, and enterprise control.
Clear roles. Sharp boundaries. One operating model.
The best public explanation is not a wall of features. It is a clean application map that shows what each part of Nexus owns and how the platform hangs together.
Designed to read like a platform, not a menu of disconnected software
The colors, titles, and app roles below create a clearer public-facing application map and a stronger sense of Nexus identity.
Point of sale for quick service and table service environments.
Kitchen execution across prep, production, expo, and handoff.
Drive-thru and service flow intelligence.
Self-service ordering experiences for high-throughput environments.
Customer-facing online ordering connected back into the operating model.
Customer identity, loyalty, offers, and profile-linked experiences.
Digital menu boards and display management.
Reporting, labor, inventory, costing, cash, and multi-site operational visibility.
Device staging, claiming, identity, and rollout control.
Diagnostics, remoting, simulation, support tooling, and device oversight.
Mobile operational access where it is useful and appropriate.
Unified entry point into the wider platform.
Physical environment and security-related operational systems.
In-store media and audio experiences as part of the wider estate.