Four days, several hundred conversations, and one question in almost every one of them: what does Kubernetes in the vehicle look like in practice? From 22 to 25 September 2026 we were at InnoTrans in Berlin, Hall 4, Booth 235. What we took home is a fairly precise picture of where the industry stands right now.
Thank You for Visiting Our Booth in Berlin
InnoTrans 2026 confirmed what has been taking shape for a while: operators and integrators no longer ask whether onboard systems should be networked and centrally managed. They ask how to run real workloads in the vehicle without building a separate operating model for the edge. And how that model stays auditable once NIS2 and the Cyber Resilience Act move from paper into tender documents.
Here is a look back at the three demos from Hall 4 – and how to continue the conversation if we missed each other in Berlin.

The Most Requested Demo: Kubernetes in the Vehicle
Unwired Edge Compute brings the same Kubernetes into the vehicle that runs in data centers worldwide. At the booth we showed how an existing cloud workload runs on board with minimal changes – and how it is managed fleet-wide through the Unwired Edge Cloud.
Why does this strike a nerve? Because onboard software today is almost always built against a device-specific stack: a vendor SDK, a proprietary container format, or a cross-compiled binary that only its original authors can maintain. Every application becomes an integration project, every fleet a special case.
Standard Kubernetes on board removes that divide. The same manifests, the same images, the same CI pipeline and the same operating tools a team already uses in the cloud apply in the vehicle as well. Passenger information, CCTV analytics, predictive maintenance agents, ticketing backends and diagnostic workloads become ordinary deployments – not bespoke firmware integrations.
This combination of a familiar developer experience and fleet-wide control was the topic we booked the most follow-up meetings on in Berlin.
NIS2- and CRA-Ready Without Rebuilding the Fleet
Compliance was the second most frequent question at the booth – and it is asked differently than a year ago. Back then, the question was what the regulation demands. In Berlin it was about evidence: who can prove on request which software version is running on which vehicle, and what happened during a specific incident?
The Unwired Edge Cloud brings modem telemetry, GPS, throughput and container metrics together in one place – hosted in the EU, ISO 27001 certified and audit-ready by default. The evidence is a query, not a reporting exercise after the fact.
One point we kept making at the booth: readiness does not require replacing the entire fleet in one go. It requires a consistent management and telemetry layer across everything that is already installed. Then visibility, update control and traceability no longer depend on which hardware generation a vehicle happens to carry.
LEO WAN Bonding: Satellite Plus Cellular Instead of Either-Or
The third demo answered a question that has become more pressing for rail since LEO constellations arrived: does satellite replace cellular, or complement it?
The answer: it complements it – if you combine the two properly. The Unwired Edge Cloud bonds 5G, 4G, LEO satellite and fixed lines at packet level. Bandwidths add up, and if one link drops, the others carry the session on without interruption. Our WAN bonding page explains how this works technically.
That is exactly what passenger and operational traffic on board need: a connection that does not end at the city limits, and one that keeps every session alive when switching between uplinks.

Let’s Continue the Conversation
Whether we talked in Berlin or you are joining now: book a personal demo of the Unwired Edge Cloud and see Kubernetes in the vehicle for your own fleet. Book an Edge Cloud demo.
Didn’t get a slot in Berlin? We’ll make up for it – wherever you are. And if you would rather talk first, just get in touch.




