Platform
The platform, layer by layer
Hybot is built from three layers. A Core RMS runs inside each venue holding the map, the task queue and the robots. A Central Platform sits above every site with one fleet view and per-project health. Guest-facing surfaces — kiosk, table QR and surveys — sit on top of both.
Three layers, and which one you need
Core RMS — inside the venue
- The map, the named points of interest, the task queue and the staff interface. Auto-assignment re-scores the whole queue every two seconds against task priority, distance to pickup and remaining battery. One site needs only this layer.
Central Platform — above every site
- One fleet view across projects with state, battery, settings and lifetime totals per robot; per-project health by heartbeat; remote commands queued and acknowledged; and selective update rollout so one site takes a release before the estate does.
Guest experience — in front of the visitor
- Kiosk ordering on an in-venue screen, table QR menus with live order tracking, and short surveys on the robot's own display. Guest requests become ordinary tasks in the same queue staff use, not a parallel system.
Capabilities in detail
Each of these is shipped functionality described in operational terms. Nothing on these pages describes a feature that does not exist.
Advertising on robot screens
Hybot can schedule media to robot screens across a venue or a whole estate, with campaigns managed centrally and measured against the fleet's own counters.
The guest-facing layer: kiosk, QR and surveys
Kiosk ordering, table QR menus, robot-body surveys and a live order tracker — the parts of Hybot your guests touch, tied to the same task queue staff use.
Robot fleet management across every site
Hybot fleet management shows every robot across every location in one view, queues remote commands, monitors heartbeats and rolls out updates per project.
How Hybot decides which robot does what
Hybot re-scores the task queue every two seconds and assigns each job by priority, distance and battery, with multi-step workflows and confirmation waypoints.
Frequently asked questions
Do I need all three layers?
- No. A single venue runs on its Core RMS alone and needs nothing above it. The Central Platform becomes worth having when you have more than one location, or when you need oversight without being able to walk into the building.
How are customer sites isolated from each other?
- Each project runs on its own subdomain with its own dedicated database. That is a more expensive multi-tenancy choice than a shared schema, and it is the one that answers a security reviewer's first question architecturally rather than with a promise.
What happens if a venue loses its internet connection?
- Local operation is handled by the Core RMS inside the building, so the venue does not lose its robots. What degrades is central oversight. Internet quality is itself reported per project and charted over the last hour, so a weak site is visible rather than mysterious.
Can we integrate our own systems?
- There is a REST and WebSocket surface for dispatching robots, creating tasks and streaming live state, behind a vendor-agnostic robot abstraction. How much work an integration is depends entirely on what your existing systems expose.
See it running
A demo shows the fleet view, the task queue and the guest-facing surfaces against a real or simulated fleet.