Why are there no numbers on this page?

Because any figure published here would either be unverified or would disclose something that belongs in a managed conversation. We would rather be judged on what we say we have built, which is checkable, than on projections that are not.

What has actually been built?

A per-site robot management system with an auto-assignment engine, a multi-tenant central platform with fleet management and per-project health monitoring, a vendor-agnostic robot abstraction layer, and guest-facing kiosk, table-QR and survey experiences. These are shipped capabilities, described across the platform pages.

What is the business model?

Hybot sells and supports deployments of robots with the software that manages them, across single venues and multi-site estates, with partner and reseller routes to market. Precise commercial structure is deal-dependent and is a conversation rather than a published page.

Who are the customers?

We do not name customers on this site unless they have agreed to be named, and none currently have. A vendor that publishes logos without permission tells you something about how it will treat your information too.

How do I start a conversation?

Use the investor contact route and say what you are looking at and at what stage. We will tell you quickly whether there is a fit rather than running a long process that neither side benefits from.

Investor or franchise seeker

Hybot for investors

Hybot is a service-robot platform built by Hyrcan-Tech: robots that deliver, collect and guide, a per-site management system, and a multi-tenant central platform overseeing several venues. This page describes what has been built rather than projections. Financials, traction and roadmap belong in a conversation under terms, not on a public page.

What this page is

An accurate description of what exists, so that a conversation can start from facts rather than from a deck. It is not a data room and it does not contain financials, traction or a roadmap. Those belong in a managed conversation.

If a company puts its projections on an indexed web page, ask why.

What has been built

Three layers, and the separation between them is the substance of the thing.

Per-site Core RMS. Runs inside the venue: map, points of interest, task queue, staff interface, and an auto-assignment engine that re-scores the queue every two seconds against task priority, distance and battery. A single venue needs nothing else.

Multi-tenant Central Platform. Each customer project runs on its own subdomain with a dedicated database for isolation. Above them sits one fleet view, per-project health monitoring by heartbeat, a queued-and-acknowledged remote command channel, and selective per-project update rollout.

Guest-facing experiences. Kiosk ordering, table QR with live order tracking, and surveys shown on the robot's own display — with guest requests entering the same task queue staff use, not a parallel one.

The structural choices worth noticing

Vendor-agnostic robot abstraction. Adapters sit behind a common model, so the product is not a reseller relationship with one manufacturer wearing a software coat.
Per-project isolation. Dedicated databases on dedicated subdomains is a more expensive multi-tenancy choice than a shared schema, and it is the one that survives an enterprise security review.
Selective rollout. Not shipping to every site simultaneously is an operational maturity signal more than a technical one.

What we will not claim

No revenue figures. No customer names — none has agreed to be named, and we do not publish logos on the assumption that nobody will mind. No market-size chart lifted from an analyst PDF. No performance numbers we have not measured on our own fleet.

The things this site does quote are measured: per-robot completed tasks and distance travelled, daily and lifetime, recorded by the platform itself.

Where to look next

Other audiences: operators, resellers, people looking for work here.

To start a conversation, use the investor route and tell us your stage and thesis.

Frequently asked questions

Why are there no numbers on this page?: Because any figure published here would either be unverified or would disclose something that belongs in a managed conversation. We would rather be judged on what we say we have built, which is checkable, than on projections that are not.
What has actually been built?: A per-site robot management system with an auto-assignment engine, a multi-tenant central platform with fleet management and per-project health monitoring, a vendor-agnostic robot abstraction layer, and guest-facing kiosk, table-QR and survey experiences. These are shipped capabilities, described across the platform pages.
What is the business model?: Hybot sells and supports deployments of robots with the software that manages them, across single venues and multi-site estates, with partner and reseller routes to market. Precise commercial structure is deal-dependent and is a conversation rather than a published page.
Who are the customers?: We do not name customers on this site unless they have agreed to be named, and none currently have. A vendor that publishes logos without permission tells you something about how it will treat your information too.
How do I start a conversation?: Use the investor contact route and say what you are looking at and at what stage. We will tell you quickly whether there is a fit rather than running a long process that neither side benefits from.

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.
Become a Hybot reseller or partner
Sell and support service robots with the software already built: a vendor-agnostic platform, multi-site oversight and per-project isolation.
Working at Hybot
How Hybot hires, what the work involves, and how to send a speculative application. We list no fake vacancies and never keep applications warm.

The next step from here

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