Is this a warehouse management system?

No. Hybot moves loads between points and records that the movement happened. It does not hold stock records, allocate inventory or plan picks. Where a warehouse management system already exists, Hybot is the transport layer underneath it, reached through its HTTP API.

Can it integrate with the system we already run?

Each deployment exposes an HTTP and WebSocket API with interactive OpenAPI documentation, including direct dispatch of a robot to a named point. That is the integration surface; anything beyond it is a project conversation rather than a configuration setting.

How is throughput measured?

Per robot, the platform tracks lifetime and daily task totals and lifetime and daily distance totals, plus time in project. Those counters are the basis for any throughput claim, which is why we quote them from a running site rather than from a model.

What happens when a robot runs low on battery?

Each robot has configurable battery thresholds and an auto-charge setting. Below its threshold a robot takes itself to charge rather than accepting new work, and the assignment loop stops scoring it for tasks until it is available again.

Do you have a warehouse deployment published?

No. Hybot's evidenced deployments are in hospitality settings. This page describes what the platform does in a warehouse-shaped problem; it does not claim a warehouse reference, and no throughput figure is offered because none has been measured in one.

Warehouses

Service robots for warehouses

A warehouse service robot moves loads between named points on a mapped floor — a pick face to a packing bench, a goods-in bay to a staging area. Hybot assigns each movement automatically by priority, distance and battery, and tracks completed tasks and distance travelled per robot so throughput is measured rather than estimated.

The honest framing

Hybot's shipped deployments are in hospitality. A warehouse is a different industry with the same underlying shape — loads moving repeatedly between fixed points on a mapped floor — and the platform handles that shape well. What it does not have is a warehouse track record, and this page will not imply one.

If an evidenced warehouse reference is what you need before a conversation, we do not have one yet. If a transport layer with an open API and a measured task and distance counter per robot is useful to you now, the rest of this page describes it.

What the platform gives a warehouse

Point-to-point movement. Every destination is a configured point of interest. A robot can be given a queued task or dispatched directly to a point through the API, which is the simplest integration a warehouse management system can make.

Automatic assignment. The queue is re-scored every two seconds and each waiting job goes to the best available robot by priority, distance and battery together. There is no dispatcher and no round-robin.

Multi-step workflows. A movement can include a confirmation waypoint, so a robot waits at a bench until someone confirms the load has been taken before it releases itself back to the queue.

Measured output. Lifetime and daily task totals and distance totals per robot, plus time in project. This is the counter set any throughput claim on this site is built from.

Integration surface

Each deployment runs its own backend with an HTTP and WebSocket API and interactive OpenAPI documentation. Robots are added, removed and reloaded without restarting the system, and a misconfigured robot is skipped at startup with a warning rather than taking the fleet down with it — which in a multi-robot site is the difference between one unit out of service and a morning lost.

The developer-facing detail is on the Hybot API and integration surface.

Fleet operations across sites

A distribution network is several projects. The Central Platform shows every robot across every project with serial, state, battery, settings and its task and distance totals, queues remote commands that robots collect on their next heartbeat and acknowledge, and rolls updates out per project rather than across the whole estate at once.

Robot fleet management across every site
Service robot battery life and charging strategy
Service robots for retail — the same movement problem with a customer watching

Frequently asked questions

Is this a warehouse management system?: No. Hybot moves loads between points and records that the movement happened. It does not hold stock records, allocate inventory or plan picks. Where a warehouse management system already exists, Hybot is the transport layer underneath it, reached through its HTTP API.
Can it integrate with the system we already run?: Each deployment exposes an HTTP and WebSocket API with interactive OpenAPI documentation, including direct dispatch of a robot to a named point. That is the integration surface; anything beyond it is a project conversation rather than a configuration setting.
How is throughput measured?: Per robot, the platform tracks lifetime and daily task totals and lifetime and daily distance totals, plus time in project. Those counters are the basis for any throughput claim, which is why we quote them from a running site rather than from a model.
What happens when a robot runs low on battery?: Each robot has configurable battery thresholds and an auto-charge setting. Below its threshold a robot takes itself to charge rather than accepting new work, and the assignment loop stops scoring it for tasks until it is available again.
Do you have a warehouse deployment published?: No. Hybot's evidenced deployments are in hospitality settings. This page describes what the platform does in a warehouse-shaped problem; it does not claim a warehouse reference, and no throughput figure is offered because none has been measured in one.

Where this fits

This page is part of Smart robotic solutions by industry. If you are working through the topic in order, these are the neighbouring pages.

Service robots for retail
Retail service robots carry stock between a back room and the shop floor, guide customers to a named location and run brand video on screen between tasks.
Service robots for healthcare
Healthcare delivery robots move supplies, samples and meals between named points on a ward so clinical staff spend less of a shift walking corridors.
Service robots for offices and workplaces
Office service robots handle internal deliveries, refreshment runs and visitor guidance between named points, and show information on screen between tasks.

Tell us about the venue

Pricing depends on unit count, layout and integration work, so we quote against a real site rather than publishing a package.

Request a quote