What does a partner get that a hardware distributor does not?

A management layer. Robots arrive with vendor software that assumes one site and one operator. Hybot adds the task queue, the staff interface, multi-site oversight and per-project health monitoring, which is what turns a hardware sale into a supportable service relationship.

Am I locked into one robot manufacturer?

No. Hybot has a vendor-agnostic abstraction layer with per-vendor adapters behind it. Which specific models are supported at any time is a question to ask us directly, because the answer changes and we will not publish a list we cannot keep current.

How are client sites kept separate?

Each project runs on its own subdomain with a dedicated database. That isolation is the thing a client's security reviewer asks about first, and it is easier to answer when it is architectural rather than a filter in a shared schema.

Can I support clients without visiting them?

Central diagnostics report per project by heartbeat: internet quality, frontend, backend and WebSocket status, vendor API reachability, charted over the last hour. Remote commands are queued and acknowledged, so you can tell whether an instruction was actually applied.

What are the commercial terms?

Deal-dependent, and we are not going to publish a margin table that will be wrong for your market. Tell us the territory, the segment you sell into and the support capability you already have, and we will discuss a structure against that.

Reseller or distributor

Become a Hybot reseller or partner

Reselling robots without management software means reselling hardware and inheriting the support calls. Hybot is the layer that makes a deployment supportable: per-site management, a multi-tenant platform with per-project health monitoring, and a vendor-agnostic abstraction so your catalogue is not tied to one manufacturer's roadmap.

The problem with reselling hardware

A robot arrives with the manufacturer's own software. It assumes one site, one operator, and someone physically present. That is fine for the demo and it is where the trouble starts, because the moment your client has three venues and you have twenty clients, your support model is phone calls and site visits.

The management layer is what changes the economics. It is also the part distributors rarely own, which is the opportunity.

What you are selling

In the venue: Core RMS — map, points of interest, task queue, staff interface, and an assignment engine that re-scores the queue every two seconds against priority, distance and battery.

Above the venue: the Central Platform — one fleet view across projects, per robot state, battery, settings and lifetime totals; per-project health; queued and acknowledged remote commands; selective update rollout.

In front of the guest: kiosk ordering, table QR with live order tracking, and surveys on the robot's own screen.

You can sell one venue on the first layer alone. The second layer is what makes the twentieth venue no harder to support than the second.

Supporting clients you cannot visit

This is the part worth your attention commercially, because it is your margin.

Each project heartbeats to the platform with internet quality measured as client-to-project latency, frontend, backend and WebSocket status, and vendor API reachability — charted over the last hour with weak, medium and strong bands. Server nodes report primary and secondary status. Per-project risk analytics rank which sites need attention first.

Remote commands are queued and picked up on the robot's next heartbeat, then acknowledged. You can tell the difference between an instruction sent and an instruction applied, from wherever you are.

Isolation, because your client will ask

Every project gets its own subdomain and its own database. When a client's security reviewer asks how their data is separated from another customer's, the answer is architectural rather than a promise about query filters.

What we will not put on this page

Margin structures, territory availability, a supported-models list that would be stale within a quarter, or partner logos. Those are conversations. Tell us your territory and segment and we will be specific.

Where to go next

Other audiences: operators, investors, advertisers.

Frequently asked questions

What does a partner get that a hardware distributor does not?: A management layer. Robots arrive with vendor software that assumes one site and one operator. Hybot adds the task queue, the staff interface, multi-site oversight and per-project health monitoring, which is what turns a hardware sale into a supportable service relationship.
Am I locked into one robot manufacturer?: No. Hybot has a vendor-agnostic abstraction layer with per-vendor adapters behind it. Which specific models are supported at any time is a question to ask us directly, because the answer changes and we will not publish a list we cannot keep current.
How are client sites kept separate?: Each project runs on its own subdomain with a dedicated database. That isolation is the thing a client's security reviewer asks about first, and it is easier to answer when it is architectural rather than a filter in a shared schema.
Can I support clients without visiting them?: Central diagnostics report per project by heartbeat: internet quality, frontend, backend and WebSocket status, vendor API reachability, charted over the last hour. Remote commands are queued and acknowledged, so you can tell whether an instruction was actually applied.
What are the commercial terms?: Deal-dependent, and we are not going to publish a margin table that will be wrong for your market. Tell us the territory, the segment you sell into and the support capability you already have, and we will discuss a structure against that.

Where this fits

This page is part of Hybot for every audience. If you are working through the topic in order, these are the neighbouring pages.

Service robots for business operators
For the person who has to justify the spend: what a Hybot deployment actually involves, what we can measure, and the questions to ask before you sign anything.
Hybot for investors
What Hybot is, what has actually been built, and what we will not claim. An honest starting point for an investor conversation rather than a pitch deck in web form.
Advertising on robots that move through the venue
Robot screens arrive beside a person at a defined moment instead of waiting on a wall. What Hybot can schedule, what it records, and what we refuse to estimate.

The next step from here

One conversation, routed to the person who can answer it rather than to a general inbox.

Apply to partner with us