Mission control for the service floor.
Your hotel bought robots. It didn't buy a way to watch them. Labornauts puts every delivery, scrubbing and mopping unit on one screen — live status, alerts that learn each machine's own normal, and a safe way to reach in when something stalls on fourteen at two in the morning.
No rip-and-replace. Your robots stay yours — an agent registers them and the console does the rest.
Delivery
Scrubber
Mop unit
Three jobs, three ways a shift goes wrong.
These are the three machines most hotels start with. None of them announce a problem — and a robot that has quietly stopped looks exactly like a robot that has quietly finished.
Room service
The jobA covered tray leaves the kitchen, takes the service lift and finds a guest door on its own — so nobody walks the fourteenth floor at midnight.
What goes wrongIt parks outside 1412 and waits. The guest is asleep, the tray is going cold, and the front desk hears about it when the guest calls down.
What you seeIt shows as stalled as soon as it stops checking in — and you send it back to its dock from the front desk, without anyone going up there.
Floor scrubbing
The jobAn overnight machine scrubs the ballroom and the lobby marble on a set route, so the day crew walks in on a finished floor.
What goes wrongA worn brush makes it pull harder for weeks before it finally gives out — always mid-ballroom, always the night before an event.
What you seeA warning while there's still time to act, because we learn what this particular machine normally does and flag it when it starts working harder than its own usual.
Mopping
The jobA small unit runs corridor passes before the breakfast rush, covering the floors housekeeping hasn't reached yet.
What goes wrongSomeone unplugs a docked unit to charge a vacuum. Nobody writes it down. The 5am corridor run silently doesn't happen.
What you seeIt turns grey on the board the moment it stops checking in — so the morning shift starts knowing which machines are actually ready, without walking the building.
Four things, done properly.
Not a feature list — this is the whole product. If you can read a booking screen, you can read this one.
Fleet
Add a machineEvery unit, one board
Where each machine is, what it is doing, how much battery it has left and when it last checked in. The board updates itself — no refreshing, no hunting. A machine that loses power marks itself stopped, so you find out from the screen instead of from a guest.
Alerts tuned to each machine
We learn what each machine normally does, then tell you when that machine drifts from its own normal. The veteran scrubber that always runs warm stops crying wolf; the new one that suddenly does gets caught. One alert per problem — not fifty.
Reach in without reaching out
From the front desk you can send a machine home, restart it, or stop it. That is the whole menu — a short, fixed list of safe actions, and there is no way to type a command of your own. The robot checks the instruction again before it acts on it, and you watch the result come back live.
A read on the last 24 hours
Ask for a summary and get the shift in a paragraph: what ran fine, what is drifting, what to look at before the evening turn. Plain sentences, no charts — the kind of thing you forward to a GM, or read out at handover.
Six words the console uses, and what they mean on your floor.
Nobody should need a robotics background to run a night shift. This is the whole vocabulary.
- Checking in
- Every machine says “still here, still working” every few seconds. Miss a few in a row and it is marked stopped — which is how you find out about a flat battery on fourteen without walking up there.
- Needs a look
- Not broken. Drifting. Something is off compared with how this machine usually behaves — a brush wearing down, a wheel starting to drag. Something to schedule, not to panic about.
- Its own normal
- We don't hold every machine to one number. A ten-year-old scrubber that always runs warm is fine; a new one that suddenly runs warm is not. Each machine is judged against its own recent history.
- Approved actions
- The short, fixed menu the console can send a machine: send it home, restart it, stop it. There is no box to type your own command into. That is deliberate, and it cannot be switched off.
- The agent
- A small piece of software that sits on each robot, checks in on its behalf and carries out those approved actions. You install it once, with one line, and never touch it again.
- Property
- Your building. Machines, staff logins and alerts all belong to it, so a duty manager at one hotel never sees another hotel's floor — useful the moment you run more than one.
Three steps, and the third is a button.
You do this once per building, and your robot supplier or IT contact can do step two. Every machine on site starts from the same code and still ends up with its own private credentials.
Create a join code for your hotel
One click in the console. The code only works for your property, expires on its own, can be capped to a number of machines, and you can cancel it at any time — so handing it to an installer is safe.
Run one line on each machine
Usually your robot supplier or IT contact. The software installs itself and swaps the join code for credentials of its own, so the shared code never stays on the machine. If a robot is ever rebuilt, running the same line again brings it back as the same machine — not a duplicate.
# on the robotcurl -sSL https://[YOUR-HOST]/agent/install.sh \ | LABORNAUTS_API_URL=https://[YOUR-HOST] \ LABORNAUTS_ENROLL_TOKEN=rbt_enroll_xxx sh
Approve it, and it appears
New machines wait in the console as New and can do nothing at all until a manager approves them — so a stranger with your join code still gets nowhere. Once you trust a site, you can let its machines come online by themselves.
The straight answers, before you ask.
Straight answers
- We do not drive your robots. Steering a machine around guests is a safety matter, and we treat it as one. Movement controls ship switched off, behind two separate locks, and your robots keep navigating the way they already do.
- Boston Dynamics Spot is watch-only today. If you run one, you see its status, battery, health and faults on the same board as everything else — but nothing is sent back to it.
- Mixed fleets are the point. Machines from different manufacturers arrive on one board, described the same way, so your staff learn one screen instead of one screen per brand.
- Every action has a name on it. Robot credentials are shown once and never again, and every instruction sent to a machine is recorded against the person who sent it — so “who sent it home?” always has an answer.
Bring one floor.
We'll put it on the board.
Twenty minutes, your actual units, your actual corridors. If the console doesn't tell you something you didn't already know, we'll say so.
Book a walkthroughOr write to john@labornauts.com
Already a customer? Sign in to your console