The intelligence layer for machines that think, decide and act.
One behavior layer across every machine class — cleaning, inspection, logistics, security, port. Your fleet stops being a dozen closed systems and starts behaving as one.
Every manufacturer ships its own closed stack. Put six vendors on one site and you get six dashboards, six schedules and no shared awareness. Our platform sits above all of them and supplies the behavior: what each machine does, when, and how it reacts to the others.
Sensor and telemetry streams from any vendor normalized into one model of the site — floors, zones, obstacles, people, other machines.
Tasks assigned against live conditions rather than a fixed timetable. A spill, a closed corridor or a late delivery re-plans the fleet, not just one unit.
Decisions bounded by written policy the machines cannot break: speed in public areas, exclusion zones, certified-area limits, handover to a human. Every decision is logged and auditable.
Execution across the whole fleet, vendors and machine classes alike. A scrubber, a patrol robot and a terminal tractor share the same map, the same rules and the same operator.
Integration runs through vendor adapters and a documented API, so a machine already on your floor can be brought under the platform without replacing it. Where a manufacturer's stack is genuinely closed, we say so before you buy rather than after.
Each class has its own manufacturers, certification path and physics. The behavior layer is common to all of them; the adapters are not.
A robot without explosion-proof certification cannot enter the areas where an operator most wants it. Certification takes up to two years and freezes the hardware design while it runs — so the competitive set will not widen quickly.
One thread for every machine on site, whoever built them. Give an instruction to all of them or to one. Watch them work it out between themselves.
Interactive demonstration. The fleet shown is simulated — the console is not connected to live machines on this page.
Machines reach the behavior layer two ways: through the open standards the industry already agreed on, or through a connector we write against a manufacturer's own interface. Either way, a machine already on your floor joins the fleet without being replaced.
The interface most of intralogistics already speaks. Published by the VDA with VDMA, it defines how a master control sends transport orders to vehicles and how vehicles report state back, over MQTT with JSON payloads. Version 3.0 landed in March 2026, adding support for freely navigating robots and a formal zone concept.
Brings in AGVs, AMRs, tuggers and autonomous forklifts without a per-brand integration.The building side of the problem. Born from getting cleaning, delivery and security robots from different vendors to share hospital corridors, it coordinates robots with each other and with lifts, doors and other bottlenecks. Managed by the Open Source Robotics Alliance.
Brings in service, cleaning and security fleets, plus the building infrastructure they have to negotiate.The framework a large share of modern autonomous machines are built on. Where a manufacturer exposes its ROS 2 graph, the machine can be brought under the behavior layer directly rather than through a vendor gateway.
Covers inspection quadrupeds, research platforms and most newer industrial autonomy.Where a manufacturer publishes its own REST or SDK interface, we write a connector against it. One connector per vendor, maintained by us and shipped to every customer running the platform.
Covers the machines whose makers have not adopted a standard, which is still most of port and heavy equipment.Manufacturer names are listed to describe connector coverage. Company logos and trade marks are the property of their respective owners and are shown only where a distribution or integration agreement is in place.
If your machines should speak this language, we write the connector with you and it ships to every customer running the platform. No licence fee to the manufacturer.
We supply the hardware as well, so a deployment can come from one place. Hardware is a one-off landed budget in US dollars excluding VAT and installation; the behavior license is monthly, per machine, and is what makes the fleet act as one.
Photography is representative of the equipment class. Manufacturer product imagery replaces it once each distribution agreement is in place.
Each sector has a different binding constraint — labour cost, heat, certification or shift coverage. We specify against the constraint.
One license per machine under management, billed monthly. Every tier includes the fleet view, vendor adapters and updates. Indicative list pricing; fleet rates apply above twenty machines.
For service, cleaning and energy machines on a known route.
For inspection, security and intralogistics, where machines must react to each other.
For certified areas, ports and anywhere a regulator asks what the machine decided and why.
Pricing shown is indicative and subject to confirmation. A paid ninety-day pilot on one floor, wing or yard is the normal way to start.
Compiled from published distributor pricing current to 2026. Treat these as budgetary ceilings — volume pricing lands materially below them.
Anyone can ship a robot into Jebel Ali. The difference is month seven, when a sensor fails in August.
TDRA type approval, ECAS conformity and, where needed, IECEx documentation are completed by us and handed over with the equipment.
Consignment stock of wear parts and critical spares held locally for every product line we carry.
Factory-certified service engineers resident in the UAE, with response times written into the contract.
Most deployments start with a paid 90-day pilot on one floor, wing or yard. Measured results first, fleet order second.
Point a camera at the code. It opens this catalogue — every division, every specification, every price — on any phone, in English or Arabic. Print it on a card, a stand, a proposal cover or an exhibition panel.
horme.site
Scan for the full catalogue
If you build autonomous systems and are evaluating representation across the UAE and GCC, we take a product from first container to a serviced installed base — and carry the regulatory work that usually stalls market entry.
HORMĒ is a Behavioral Intelligence platform for autonomous machines, based in Dubai. It puts cleaning, inspection, logistics, security and port machines from different manufacturers under one behavior layer, so a mixed fleet can be run as one.
No. Machines connect through open standards (VDA 5050, Open-RMF, ROS 2) or through a connector written against the manufacturer's own API, so a machine already on your floor can join the fleet without being replaced. Where a vendor's stack is closed, we say so before you buy.
The behavior license is priced per machine, per month: Core from $149, Autonomy from $349 and Assured from $690. Pricing is indicative, and fleet rates apply above twenty machines. Hardware is a separate one-off purchase.
Most deployments start with a paid 90-day pilot on one floor, wing or yard. Results are measured first, and the fleet order follows.
Typically 8 to 16 weeks to site. An October order usually lands in Q1 from Asian and Israeli suppliers; European platforms arrive in Q2.
Twelve machine classes, including delivery and service robots, commercial cleaning robots, security and patrol robots, inspection robots for oil and gas, warehouse robots and autonomous forklifts, port and heavy equipment, marine safety systems and solar panel cleaning robots.
HORMĒ completes TDRA type approval, ECAS conformity and, where needed, IECEx documentation before shipment, holds spare parts in the UAE, and uses factory-certified service engineers based in the UAE with response times written into the contract.
We will confirm stock, final landed pricing and delivery dates within one working day. Nothing has been charged — payment is taken once the quotation is countersigned.