Hospital logistics orchestration. The operating core, dispatching robots and human couriers from one system, and generating the mission context every other unit depends on.
Nine live use cases
CE certified
Epic / Cerner / SAP
Robot-agnostic
InternetPeople and machines. AMRs and AGVs, humanoids, robotaxis, shuttles, drones, haulers — and the couriers walking beside them. One layer that knows them all, coordinates them all, and proves every action was allowed. It has been in production since December 2025.
02:14:03 Mission validated 02:14:05 Destination authorised 02:31:22 Execution complete 02:31:24 Record signed
One layer, every class
What the layer does
Not a fleet tool for one machine class. The same four jobs, whether the thing moving is a courier on foot, an AGV in a warehouse, a shuttle on a campus or a drone overhead.
Basis. Strategy statement of the company. The orchestration and enforcement layers are in production in healthcare logistics today; the vehicle, aircraft and humanoid classes are addressed by the same platform and regulatory requirement, and are not yet deployed revenue.
Knows
Every asset, every person, every payload, every route, in one live picture.
Coordinates
The right task to the right resource — machine or human — without a dispatcher in the middle.
Optimises
Time, cost and energy, continuously, so the organisation keeps moving.
Enforces
Everything gets where it must go, and nowhere it must not. Proven, logged, defensible.
The thesis
A robot, a vehicle, a drone, a person on a shift — none of them generates its own mission, its own authorisation, or its own power. Machine makers sell hardware. Cyber vendors see devices. We hold all three layers in between.
Basis. Strategy statement of the company. Production status of the orchestration layer is described under Proof in production below.
Mission
Who moves it, and when. Our orchestration platform generates that decision in production today — and it is the industry’s first to dispatch machines and human workers from one system.
Permission
Three regulatory regimes now demand evidence that a physical action was authorised. No vendor sells that evidence. We generate the authorising order already.
Power
A fleet that needs a person to plug in a cable is not autonomous. Removing the last human hand is the layer we intend to acquire rather than build.
A person, a system, or a schedule.
What moves, where to, carrying what.
Before the action, not after it.
Denied, and the denial is itself a record.
Machine or person, tracked throughout.
Evidence a regulator accepts.
The moment
Machines now take plain-language commands and choose their own route and timing. The tooling that governs them still assumes a human is holding the controls.
Basis. Vulnerability disclosure: Cynerio JekyllBot:5, April 2022, affecting Aethon TUG hospital couriers; severity as recorded by NVD. Regulation: Directives and Regulations (EU) 2022/2555, 2024/2847 and 2023/1230.
Autonomous couriers accept natural-language commands and set their own priority, route and timing. Prompt injection stopped being a text problem and became a physical one.
Five zero-days were disclosed in hospital courier robots at a maximum CVSS of 9.8, requiring no privileges. A software flaw stopped being a data problem and started being a physical one.
NIS2 is in force, Cyber Resilience Act reporting began in September 2026, and the EU Machinery Regulation follows in 2027. Machines that move in the physical world are being told to account for themselves.
Proof in production
Sheba Medical Center, the #7 hospital in the world, 1,700 beds. Machines move time-critical chemotherapy between pharmacy and oncology across multiple buildings — through elevators, doors and gates, indoors and out. Healthcare is where the layer is proven, not the limit of where it applies.
Basis. Company-reported from the Sheba Medical Center deployment, August 2026. Not independently audited. Hospital ranking per Newsweek World's Best Hospitals. Figures describe the chemotherapy use case, not a group-wide average.
Most of this category is still running trials. The distinction that matters is volume over time, in a live building, with no one standing next to the machine.





It directly impacts the continuum of care, shortens waiting times and reduces the burden on medical teams. It is a model of digital transformation implemented in practice in the field.Prof. Eyal Zimlichman, MD — Chief Transformation, Innovation & AI Officer, Sheba Medical Center
Also live. CE certified for crowded clinical environments, operating 24/7 alongside staff. Integrated with elevators, doors, gates, Epic, Cerner and SAP with no infrastructure changes. Nine use cases running: chemotherapy, lab samples, blood, medication, supplies, equipment, linen, meals, patient transport. US platform launched July 2026.
Why now, everywhere
Every year more autonomous machines are deployed, and every year fewer people are available to do the work those machines are bought for. Today both sides are coordinated by hand — a dispatcher, a phone, a whiteboard, a spreadsheet.
Basis. Third-party figures, cited as published and not company estimates. Robotaxi fleet projection per Goldman Sachs; humanoid shipments and AMR installed base per published industry trackers; global talent shortfall per Korn Ferry; driver shortage per IRU. Each needs a dated citation before launch. This is the direction of demand, not a sizing of our market.
The supply of machines is scaling
Robot makers are solving the machine. None of them is solving what tells a mixed fleet what to do, or proves it was allowed to.
The supply of people is not
Automation is bought to close this gap. But a machine with no mission and no authority does not close it — it moves the coordination problem somewhere else, and usually back onto a person.
A warehouse moving a pallet, a plant moving a part, a data centre moving a failed drive, a campus moving people, an operator moving a vehicle through a city, a hospital moving a controlled drug — different payloads, identical question. What moves, who moves it, was it allowed, and can you prove it afterwards.
The layer is indifferent to the vertical. Healthcare is simply where we proved it first, because it is where the tolerance for getting it wrong is lowest — not because it is the size of the opportunity.
The group
Every line stands on the same operating core. The core is live and generating the context the others need, which is why the products built on top of it cost 40–50% of building from zero.
Basis. Ownership and stage as reported by the company. Build-cost saving is a management estimate. Products marked in development are not announced, carry no committed launch date, and may change or not ship. The motion-layer transaction has not closed, the target is not disclosed, and its figures are management-reported by that company, subject to confirmatory diligence. The interest in Quantum X Labs Inc. is disclosed in the company’s periodic filings; its size, carrying value and market value are not restated here — see the filings. Quantum X Labs is described as it describes itself, in its own published materials, including its holdings in Gix Media Ltd. and Metagramm Software Ltd.
Hospital logistics orchestration. The operating core, dispatching robots and human couriers from one system, and generating the mission context every other unit depends on.
Nine live use cases
CE certified
Epic / Cerner / SAP
Robot-agnostic
A second orchestration product
100% owned — in development
The same engine, pointed out the front door. It extends the layer past the walls of the facility, onto infrastructure that already exists — which is why it costs a fraction of building from zero.
Not announced
Design-partner stage
Built on the operating core
40–50% of build cost
The trust layer
100% owned — in development
Cybersecurity for physical AI. Proof that the thing that moved was allowed to — a policy gate before the action, a signed mission object, and an immutable audit trail behind it.
Not announced
Signed mission objects
Policy gate before action
Immutable audit trail
The motion layer
In process — not closed
The machine itself. Level 4 autonomy, fleet software of its own, and a signed enterprise customer base that would take years to build from scratch.
Target not disclosed
L4, no human in loop
Granted autonomy patents
Signed customers
The power layer
Pipeline — to acquire
Energy delivery without a human hand. A fleet that needs someone to plug in a cable is not autonomous, so the last layer of the stack is one we intend to buy rather than build. Targets are under evaluation and are not disclosed.
Removes the last
human hand
Autonomous depots as
the strategic prize
Listed holding — Nasdaq: QXL
An Israel-based quantum technology company, separately listed — computing, software and sensing, with applications in aerospace, defence and clinical analysis. It is also where the group’s digital advertising business sits: Gix Media is held by Quantum X Labs, alongside Metagramm. A holding, not a layer — it sits outside the orchestration strategy and is not part of the case this page makes. The holding in full.
Nasdaq: QXL since
30 Apr 2026
Computing, software, sensing
Holds Gix Media
Why it compounds
A robot company sells you a robot. We sell the decision that told the robot to move, the machine that moved, the proof it was allowed to, and the power that lets it do it again an hour later.
Basis. Strategy statement. The motion layer depends on completing a transaction that has not closed, with a target that is not disclosed, and the energy layer on a future acquisition; neither is secured. No single account buys every line today — that is the growth case, not the base case.
Trust
In development
Turns an operational log into audit evidence a regulator accepts.
Motion
In process
The L4 machine that executes the mission, with no human in the loop.
Energy
To acquire
Removes the last human hand. No cable, no plug, no operator.
A competitor has to win four arguments to displace us. We have to win one to keep the account. The layers are not adjacent businesses bolted together — the mission object generated at the dispatch layer is the input the trust layer needs, and the machine layer is the thing the mission commands.
The commercial consequence. Multiple revenue lines on one invoice, inside an account we already hold. One 400-bed hospital can carry all of them.
The next layer
When a machine opens a door or moves a controlled payload, the security question is no longer whether the device was patched. It is whether the action was allowed.
Basis. The requirement is public: from 20 January 2027, Annex III 1.1.9 of Regulation (EU) 2023/1230 obliges a machine placed on the EU market to collect evidence of legitimate or illegitimate intervention. What we are building against it is in development and not announced.
What today’s tools record
Satisfies part of a cybersecurity control. Says nothing about what the machine then did.
What none of them record
Whether the action that followed was permitted — by whom, on what authority, and against which instruction.
Cybersecurity proves the machine was trusted. Nobody yet proves the action was allowed. We already generate the authorising order, which is why this layer is ours to build rather than ours to buy.
It is one of several layers we intend to hold above everything that moves. We are not describing the product here.
How we earn
Software by subscription, the machine itself as a service, and the work of getting both running. The first two are recurring and multi-year. Every new layer we add is sold through the same three, into accounts we already hold — not as a new business with a new sales motion.
Software
A platform licence per site, per year, plus seats for the people dispatched alongside the machines. It grows with the number of sites and the number of jobs the layer is trusted with.
Recurring, multi-year, and it expands inside the account.
Machines
The machine as a service, per unit, per month. The customer buys the work being done rather than a capital asset to depreciate, which moves the decision out of a capital budget and shortens it.
Recurring, and it scales with fleet size.
Services
Deployment and integration to get a site live, then maintenance and support to keep it live. Integration into the systems a site already runs is most of the reason the layer is hard to displace once it is in.
Deployment is one-time and the lowest-margin line we carry. Maintenance and support are recurring.
The same three lines, sold across a widening surface. Each step is a bigger share of the same customer, not a different company.
The power layer is the exception, and the interesting one. Energy delivery can be sold as capital equipment to the operator, or supplied to the platform vendors themselves — the makers of the robots, the humanoids, the robotaxis. That is a different customer from every line above it: we would be selling into the people building the machines rather than the sites running them.
Why this compounds. A new layer inherits the customer, the contract and the mission data. That is why the second and third products cost 40–50% of building from zero.
Live
Coordinating everything that moves within a facility — machines and people, one system.
In development
The same engine past the walls: out of the building, onto the road, into the field.
In development
Proof that each action was permitted. Attaches per authorised machine, and can ship inside a manufacturer’s own product.
To acquire
Level 4 motion, so the thing carrying out the mission is ours as well as the mission.
To acquire
Energy delivery with no cable and no operator. Sold as capital equipment to the operator, or supplied to the platform vendors — from robot makers to robotaxi fleets.
What we buy next
We buy what makes the layer harder to leave. A US listing is the currency for that, and we have one — Nasdaq is where physical-AI comparables are priced, and where the next transactions get funded.
Basis. Acquisition strategy as approved by the board of the listed parent. One transaction is in process and has not closed; further targets are under evaluation, are not disclosed, and no agreement exists. No transaction described here is certain to complete.
Owned and live
Built
The operating core and the context engine, with two further products in development on top of it at 40–50% of build-from-zero cost.
The operating core,
live in production
+ two products
in development
In process
Not closed
The machine layer: Level 4 autonomy IP, granted patents, and a signed enterprise customer base that would take years to assemble.
Target not disclosed
Confirmatory diligence
Completion not certain
Under evaluation
Pipeline
The power layer, and anything else a mission has to pass through: dispensing automation, lab handling, specialised payload robots, or a second geography for the orchestration platform.
The filter: does it make
the layer harder to leave?
We own the layer that decides what moves and proves it was allowed to. Next we buy the machine that moves, and the power that keeps it moving.
Important notice
This website is for information only. It is not an offer to sell, or a solicitation of an offer to buy, any security, and it is not a prospectus. Any offering would be made only by means of a prospectus or offering document filed with the relevant authority.
Statements about strategy, markets, acquisitions, listings and future performance are forward-looking. They rest on assumptions that may prove wrong, and actual results may differ materially. Nothing here is a guarantee of future performance, and the company undertakes no obligation to update these statements.
Every material figure on this site is labelled in the margin beside it: sourced to a named document, an internal estimate or assumption, or not yet prepared. Nothing sits between those states. Company-reported operational figures have not been independently audited.
One transaction, described on this site as the motion layer, has not closed. The target is not named, because neither the transaction nor its counterparty has been announced. Target-company figures are management-reported by that company and are subject to confirmatory diligence. Completion is not certain. Further acquisition targets are under evaluation only, and no agreement exists.
The company is Gix Internet Ltd. Its ordinary shares trade on the Nasdaq Capital Market under GIXI and on the Tel Aviv Stock Exchange under GIX.
Lines described on this site as in development are not announced products. They have no committed launch date, no released pricing, and no validated customer contract. They may change materially, or not ship at all. Nothing here should be read as a commitment to deliver them.
Where this site refers to regulatory requirements, the company's products address named requirements within those regimes. The company does not sell conformity, certification or legal compliance, and does not act as a conformity assessment body.
Display settings
These settings are kept in your browser on this device. Nothing is sent to us.