{"id":8684,"date":"2026-09-30T09:00:00","date_gmt":"2026-09-30T09:00:00","guid":{"rendered":"https:\/\/unwirednetworks.com\/innotrans-2026-recap\/"},"modified":"2026-09-30T12:47:40","modified_gmt":"2026-09-30T12:47:40","slug":"innotrans-2026-recap","status":"publish","type":"post","link":"https:\/\/unwirednetworks.com\/en\/innotrans-2026-recap\/","title":{"rendered":"InnoTrans 2026 Recap: Kubernetes in the Vehicle Was the Question of the Show"},"content":{"rendered":"\n

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.<\/p>\n\n\n\n

Thank You for Visiting Our Booth in Berlin<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

Here is a look back at the three demos from Hall 4 \u2013 and how to continue the conversation if we missed each other in Berlin.<\/p>\n\n\n

\n
\"The<\/figure>\n<\/div>\n\n\n

The Most Requested Demo: Kubernetes in the Vehicle<\/h2>\n\n\n\n

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 \u2013 and how it is managed fleet-wide through the Unwired Edge Cloud<\/a>.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

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 \u2013 not bespoke firmware integrations.<\/p>\n\n\n\n

\n
\n
\n
\n
<\/path><\/svg><\/div>\n
Standard Kubernetes on board<\/div>\n
No vendor SDK, no proprietary container format. What runs in the data center runs unchanged on the vehicle router.<\/div>\n <\/div>\n <\/div>\n
\n
\n
<\/path><\/svg><\/div>\n
One pipeline all the way into the vehicle<\/div>\n
From the ticketing backend to CCTV analytics: onboard applications go through the same CI\/CD as any other workload.<\/div>\n <\/div>\n <\/div>\n
\n
\n
<\/path><\/svg><\/div>\n
Rollout, staging, rollback<\/div>\n
The Unwired Edge Cloud distributes workloads by vehicle group, staggers updates, rolls back and shows the state of every vehicle \u2013 without a single SSH session.<\/div>\n <\/div>\n <\/div>\n <\/div>\n

This combination of a familiar developer experience and fleet-wide control was the topic we booked the most follow-up meetings on in Berlin.<\/p>\n<\/div>\n\n\n\n

NIS2- and CRA-Ready Without Rebuilding the Fleet<\/h2>\n\n\n\n

Compliance was the second most frequent question at the booth \u2013 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?<\/p>\n\n\n\n

The Unwired Edge Cloud brings modem telemetry, GPS, throughput and container metrics together in one place \u2013 hosted in the EU, ISO 27001 certified and audit-ready by default. The evidence is a query, not a reporting exercise after the fact.<\/p>\n\n\n\n

\n
\n
\n
\n
<\/path><\/svg><\/div>\n
Evidence on request<\/div>\n
Software version per vehicle, events per incident: documented during operation, not pieced together afterwards.<\/div>\n <\/div>\n <\/div>\n
\n
\n
<\/path><\/svg><\/div>\n
Telemetry in one place<\/div>\n
Modem, GPS, throughput and container metrics in a single layer \u2013 instead of spread across several tools.<\/div>\n <\/div>\n <\/div>\n
\n
\n
<\/path><\/svg><\/div>\n
Hosted in the EU, ISO 27001<\/div>\n
Audit readiness is part of operations \u2013 not a project restarted before every audit.<\/div>\n <\/div>\n <\/div>\n <\/div>\n

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.<\/p>\n<\/div>\n\n\n\n

LEO WAN Bonding: Satellite Plus Cellular Instead of Either-Or<\/h2>\n\n\n\n

The third demo answered a question that has become more pressing for rail since LEO constellations arrived: does satellite replace cellular, or complement it?<\/p>\n\n\n\n

The answer: it complements it \u2013 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<\/a> explains how this works technically.<\/p>\n\n\n\n

\n
\n
\n
\n
<\/path><\/svg><\/div>\n
Bonding instead of failover<\/div>\n
Failover switches over and tears down the session in the process. Bonding at packet level uses all links at the same time.<\/div>\n <\/div>\n <\/div>\n
\n
\n
<\/path><\/svg><\/div>\n
5G, 4G, LEO and fixed lines<\/div>\n
All available uplinks are bonded into one connection \u2013 with the sum of their bandwidths.<\/div>\n <\/div>\n <\/div>\n
\n
\n
<\/path><\/svg><\/div>\n
Continuous along the whole route<\/div>\n
Cellular is strong in urban stretches and thin in between; satellite is available everywhere, but with its own latency profile. Together, each covers the other’s weaknesses.<\/div>\n <\/div>\n <\/div>\n <\/div>\n

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.<\/p>\n<\/div>\n\n\n

\n
\"Demo<\/figure>\n<\/div>\n\n\n

Let’s Continue the Conversation<\/h2>\n\n\n\n

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<\/a>.<\/p>\n\n\n\n

Didn’t get a slot in Berlin? We’ll make up for it \u2013 wherever you are. And if you would rather talk first, just get in touch<\/a>.<\/p>\n\n","protected":false},"excerpt":{"rendered":"

Four days at InnoTrans 2026 in Berlin, hundreds of conversations, one question on repeat: what does Kubernetes in the vehicle look like in practice? Our recap.<\/p>\n","protected":false},"author":2,"featured_media":8681,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[43],"tags":[],"class_list":["post-8684","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"_links":{"self":[{"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/posts\/8684","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/comments?post=8684"}],"version-history":[{"count":1,"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/posts\/8684\/revisions"}],"predecessor-version":[{"id":8685,"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/posts\/8684\/revisions\/8685"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/media\/8681"}],"wp:attachment":[{"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/media?parent=8684"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/categories?post=8684"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unwirednetworks.com\/en\/wp-json\/wp\/v2\/tags?post=8684"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}