Technology
What sits underneath, for whoever wants to look.
Technology justifies the product; it is not the product. This page exists for the technical lead, the data owner and the sceptic: models, memory, integrations, isolation and how far an employee decides on its own.
How it works
Knows. Does. Runs it.
Three layers. The Brain remembers, the employees execute and the OS sets the limits. Only the middle one is hired; the other two come with every employee.
01 · HIRO Brain
Knows.
The Archivist
Your restaurant remembers.
Everything the house knows about a guest lives here, and every employee reads from it and writes to it. Who they are, how many times they have come, what they ordered, what they cannot eat, what happened last time. It is not a database someone fills in: it writes itself from every conversation, every booking and every service.
- Customer memoryOne guest across channels and venues. The one who books on WhatsApp, dines at venue two and leaves a review is the same person.
- Business contextHours, menu, allergens, policies, which table is which. What a new hire takes weeks to learn.
- IntelligenceSix segments recalculated nightly, patterns, drops, opportunities. Every recommendation cited to the data behind it.
- Ask it in plain languageBetaThe Copilot: ask about a guest, a table or a dish and it answers with the citation.
02 · The employees
Does.
Work done, not suggested.
Each employee has a post, a set of capabilities, tools and limits. It reads the memory before acting, acts on the tools you already use, and writes what it did back into the memory, so the next employee does not start from zero.
- A postBookings, customers, groups and events, comms, reviews, floor. Each does one thing and does it whole.
- The house toolsCoverManager, WhatsApp, email, the POS. It works on top of what you have, not instead of it.
- A status in plain sightLive, beta, in development or planned. On every card, on every capability. You never have to guess what is built.
03 · HIRO OS
Runs it.
The limits, written down.
The infrastructure that lets employees work without anyone watching over them: who each one is, what it can touch, how far it decides on its own and when it hands the conversation to a person. It is not bought. It comes with every employee.
- Identity and permissionsEach employee acts under its own name and its own permissions. What it did is recorded as its own.
- Limits and escalationHow far it decides alone, and when it hands off to a person. A last-minute cancellation for twelve is not one it closes by itself.
- Isolation per houseOne restaurant's data is not reachable from another. The cross-tenant leak test runs on every continuous integration.
- Multi-locationOne group, one memory. A regular at one venue is recognised at the others.
The Brain's interface
BetaAsk the memory.
Cited recommendations are live: the Analyst tells you who to call and why. Asking it in plain language, like a person, is in beta. Engine: Anthropic Claude to reason, Voyage to remember. Neither trains on your data.
Guest profile
The whole guest, cited to the data.
Visits, spend, segment and what HIRO sees today, with the recommendation and one click to the data behind it.
The ecosystem
You do not change tools. You put a team on top of them.
Your booking system stays. Your POS stays. Your WhatsApp stays. HIRO is the layer that reads them, connects them and acts on them. Every piece states what state the integration is in and what it does not cover yet.
Bookings
CoverManager
LiveReal availability, creation, modification and cancellation of the booking. The employee does not leave a note for someone to key in later, the booking is made.
Concierge · Customer · Community · Operations · Sales · Revenue
Communication
WhatsApp Business API
LiveOfficial Meta API, with the house's verified number. No grey bots, no accounts at risk of being blocked.
Bulk campaigns depend on Meta-approved templates, and that approval is not ours to control.
Concierge · Community · Reviews · Marketing · Sales
Redes sociales
BetaThe direct messages that arrive through the house profile, read and sorted before they reach your team.
Today it is direct messaging. Publishing content, replying to public comments and managing ads are out of scope.
Community
Email transaccional
LivePost-visit, reminders and email campaigns on your own domain, with managed opt-outs and controlled bounces.
Reviews · Marketing · Sales
Operations and sales
TPV · Revo
BetaReading the closed ticket to know what was actually consumed, not just who booked.
Today it reads. Writing back to the POS, and POS systems beyond Revo, are being built.
Customer · Operations
VTC
In integrationRequesting the car linked to the booking so it waits when the guest leaves.
In integration, not available yet. Requires a business account with the VTC provider.
Concierge
Engine
Anthropic Claude
LiveThe reasoning engine behind every employee. A provider with a no-training policy on your data.
Concierge · Customer · Community · Reviews · Marketing · Sales · Revenue
Voyage
LiveThe embeddings that let the house memory be searched by meaning instead of by exact word.
Customer
If your booking system is not on this list, tell us. What we integrate depends on whether it exposes an API, not on whether it suits us.
The proof
Checkable, not promised.
You will not find an improvement percentage or a guest counter here. You will find what you can verify yourself: what it integrates with, over which channel, with which engine and with what isolation.
Customer names and testimonials arrive when they are signed, not before.
Bookings
CoverManager integration in production
Real availability, creation, modification and cancellation. The booking is made in the system, not noted down for someone to key in later.
Channel
Official Meta WhatsApp Business API
The house's verified number, no grey bots, no accounts exposed to being blocked. We write about how it works underneath in the insights.
Isolation
Multi-tenant architecture with row-level isolation
One house's data is not reachable from another. The cross-tenant leak test runs on every continuous integration.
Engine
Anthropic to reason, Voyage to remember
Providers with a no-training policy on your data. Your guests do not end up inside anybody's model.
Real product
This is not a render. It is the product recorded live, with a demo restaurant and synthetic data.
See The Analyst, no makeup