About
About Hybot
Hybot is a service-robot platform built by Hyrcan-Tech. It runs robot fleets in restaurants, hotels and similar venues: assigning tasks automatically, navigating multiple floors, taking guest orders and managing every robot from one dashboard. The software is ours; the robots themselves come from hardware manufacturers we integrate with.
What we build
Hyrcan-Tech builds three things that work together. A Core robot management system runs inside each venue and holds the floor plan, the named points of interest and the task queue. A central platform sits above every site and gives one view of every robot across every project. And a guest-facing layer — kiosk ordering, table QR menus and on-robot surveys — turns a visitor’s request into an ordinary task in the same queue staff already use.
The reason the split matters is operational rather than architectural. A single restaurant needs nothing above its own building and should not pay for it. A group with eleven sites needs to know which of them has a robot that has not reported in for an hour, and cannot find that out by walking the floor.
How we work with hardware
Robots are integrated behind an abstraction rather than wired in directly. In practice that means the task queue, the map and the staff interface do not know which manufacturer built the machine carrying the tray. The developer-facing page describes the integration contract, and how service robots navigate explains what the robot itself is responsible for.
What we will not claim
These are editorial rules, applied to every page on this site including the ones written to sell.
Say what exists, not what is planned
- Every capability described on this site is shipped functionality. Roadmap items are not written in the present tense, because a prospect cannot tell the difference and will discover it at the worst possible moment.
No number we cannot source
- There are no savings percentages, delivery counts or uptime figures anywhere on this site. Where a number would be useful, we publish the method for measuring it in your venue instead.
No customer named without permission
- Deployment pages exist for customers who have agreed to appear. Anonymous case studies with invented specifics are a common industry practice and we are not going to adopt it.
Hardware honesty
- We write software. Battery life, payload and drive performance are properties of the robot you buy, so those questions get answered by the manufacturer's specification, not by us paraphrasing it.
Who writes here
Each author page lists the responsibilities behind the byline, so you can judge whether the person writing about task assignment has actually built one.
Hybot technical lead
Technical lead, Hyrcan-Tech
Hybot operations lead
Deployment and operations lead, Hyrcan-Tech
Frequently asked questions
Does Hybot make the robots?
- No. Hybot is the software layer. Robots are integrated through a vendor-agnostic abstraction, with the AutoXing Mars platform supported today, so a venue is not locked to one manufacturer's control software for the lifetime of the fleet.
Why does this site publish so few numbers?
- Because we will not publish a figure we cannot stand behind. Savings percentages, delivery counts and uptime claims are trivially easy to invent and almost never audited, and a single unverifiable number undermines every accurate statement around it.
Who writes the technical content here?
- The people who build and deploy the platform. Bylines currently name the role rather than the individual, because nobody has yet agreed to be published under their own name, and attributing to a real role is more honest than inventing a person or hiding behind a team name.
Where is Hybot deployed?
- Deployments are documented on the projects section of this site as each customer agrees to be named. We do not list venues that have not given permission, and we do not describe pilots as customers.
Ask us something specific
Enquiries route by topic, so a technical question reaches someone who can answer it rather than a sales queue.