Hubl talks to the systems you already run
Your EPOS knows the menu. Your sensors know the fridge temperatures. Your board pack knows what the business looks like. Hubl is built on an open API, so the checks, temperatures and allergen records it holds can connect to all of them — and Orbit, Hubl’s AI assistant, answers from the lot.
Built on a documented API that runs every part of the app
What Hubl can connect to
Six examples, each built to how you run rather than picked off a shelf.
- EPOS and menusNew dish on the till, allergen matrix updated.
- Temperature sensorsFridges logged overnight, nobody on site.
- Maintenance systemsA failed fridge becomes a job with an owner.
- New sites and openingsOpens with its checks already set up.
- Reporting and dashboardsCompliance alongside sales and labour.
- Training and documentsLevel 2 certificates on the right tablet.
Why it matters
1 Nothing typed twice
A dish added to the till, a site opened in your property system, a certificate filed by HR: entered once, right everywhere. The allergen matrix is the record you cannot afford to have out of step with the menu.
2 Failures become actions
A fridge at 9°C is logged, the corrective action is written — and the maintenance job raises itself. When an officer asks what you did about it, the answer includes who fixed it and when.
3 Compliance where the business looks
Put completion rates and open issues in the report the board already reads, and a site that is slipping shows up in the monthly review rather than at the next inspection.
Integration questions, answered
Does Hubl have an API?
Yes. Everything the app does, it does through Hubl’s own documented API — checks, temperature logs, products and allergens, issues, documents, reporting. That is what makes connecting other systems possible: anything your team can do in Hubl, a connected system can do too.
What can Hubl connect to?
The six on this page are the ones operators ask about most: EPOS and menu systems, temperature sensors, maintenance and facilities systems, new-site set-up, reporting and dashboards, and training or document systems. Integrations are built to how you run rather than picked off a shelf, so if your system isn’t listed, tell us what it is.
Do I need an integration to use Hubl?
No. Hubl works on its own from the first shift, on a phone or tablet. An integration is for when the same information is being typed in two places, or when a failure in Hubl should become an action somewhere else. And nothing depends on it — if the other system is unavailable, Hubl carries on as before.
Is connected data secure?
Access is granted per customer and limited by role, so a connected system only sees what it should. Every record written through the API carries the same timestamp and named person as a check done on a phone, so an integration adds evidence rather than diluting it.
What does Orbit do with connected data?
Orbit is the AI assistant built into Hubl, and it answers from your own records rather than the open internet. The more of your operation Hubl holds — menus from the EPOS, readings from sensors, certificates from your training system — the more Orbit can answer without anyone going to look: which dishes contain sesame since Tuesday’s supplier change, which fridges failed overnight, whose Level 2 expires this month. Meet Orbit.
How do we get started?
Tell us the system you run and the job you want to stop doing twice. We map out what connects, in which direction, and what it will do for the kitchen — then build it with you and prove it on one site before it goes anywhere else.
Tell us what you want Hubl to talk to
Bring us the system and the job you want to stop doing twice, and we’ll map out how it connects.
Talk to us about connecting Hubl