A robot that takes over journeys should relieve your daily work, not export your data. In hospitals, at utilities, and in other sensitive environments, the question of where operational data flows often decides whether a project starts at all. The good news: service robotics can be run so that data stays inside your environment.
The problem with cloud-bound robots
Many robots are built around their vendor's cloud. Maps, tasks, telemetry, and sometimes sensitive environmental data travel through external services. For private households that may be fine. In regulated environments it creates three problems: you lose control over data flows, you depend on the availability of an external service, and you tie yourself to one vendor.
What on-premise and offline actually mean
On-premise means control runs in your environment, on your infrastructure. Offline-capable means operation works even without a continuous internet connection, for example in areas where no external traffic is wanted. In practice it is rarely black and white. Often the time-critical coordination runs locally while selected, non-critical functions are deliberately exposed outward. What matters is that you set that boundary, not the robot vendor.
How Axiona enables this
Axiona is the layer between robots and the outside world, built for encapsulated, auditable operation. Task coordination, door and elevator integration, and the connection to third-party systems all run through a common integration layer that you operate on-premise or offline. You connect robots through adapters instead of coupling them to a foreign cloud. So you decide which data stays local and which leaves at all.
A realistic note: which modes are possible depends on the product, the compliance requirement, and the specific robot model. We assess that per project rather than making blanket promises.
Evidence from real operation
The technology comes from the SMART FOREST 5G Clinics research project at Deggendorf Institute of Technology and has been in real operation since 2023 in two hospitals. There the platform drives elevator integrations on-premise, for example a GWH LiSA10 connection for a Keenon W3. You can check which models are offline- and elevator-capable in our service robot comparison.
Next step
If where your data lives is a criterion, set the operating model early. Talk to us about your requirements, or go deeper on our approach under sovereignty and security.