Passenger Wi-Fi Is Not a Hardware Project
The CRA turns Wi-Fi into an ongoing software and operations job for OEMs, operators, and authorities
Passenger Wi-Fi in 2026 means heterogeneous fleets, different vehicle platforms, different onboard communications. Trains run for decades, but connectivity and software age fast. Maintenance windows are scarce, service providers change, network providers change. And suddenly a supposedly simple Wi-Fi project becomes a permanent problem: unreliable quality, sluggish fault clearance — and every change is a risk.
Why the Old Approach Fails
“Install once” meets lifecycles measured in decades
The old approach rests on assumptions that no longer hold: updates come rarely (or are avoided altogether), documentation is handed over once, and faults get fixed “at the next depot visit”. At the same time, the basis for professional operations is often missing: a clean software inventory, consistent visibility into system state — and above all a safe, fleet-wide rollout with dependable rollback.
Why the CRA Redefines Procurement
And why right now.
On top of that comes compliance pressure — above all from the upcoming Cyber Resilience Act (CRA). “It works today” will no longer be enough. Suppliers are increasingly expected to prove their lifecycle capabilities: clearly defined support periods, dependable patchability, professional vulnerability management, and solid evidence.
That has a very practical consequence for your budget: lifecycle security is not a one-off cost item, it is a running one. The smoothest and, in total, most economical route is therefore to treat passenger Wi-Fi as a managed service from the start.
The CRA also raises the pressure on security features at hardware level — secure boot or trusted hardware, for example. When requirements like these show up in tenders, retrofitting gets expensive fast — particularly where passenger Wi-Fi was originally procured as a hardware purchase rather than a lifecycle-managed service.
Why Passenger Wi-Fi Fails in Daily Operation
In tenders and conversations, passenger Wi-Fi often gets reduced to bandwidth. Bandwidth is a precondition — but operational reality is decided by other factors: uplink instability, captive portal and authentication failures, configuration drift across different vehicle types, no end-to-end visibility, and fear of updates because rollback is complicated or simply not possible.
The CRA does not mandate “stable uplinks”. But it makes instability expensive: remote lifecycle management becomes an obligation, not an option.
The Better Approach: Run Passenger Wi-Fi as a Service, Not as a Project
With Unwired you are not buying a box. You subscribe to a passenger Wi-Fi service that delivers a clearly defined set of functionality reliably over time — across different hardware platforms too. At the same time we take on the central obligations driven by the CRA and NIS2: incident readiness and reporting, security updates, and continuous software development — so you cover regulatory changes and developments on the end-user side (new browser versions, for instance) cleanly.
A dependable passenger Wi-Fi service rests on three pillars:
- Reliable operation at fleet scale
What you need for it: fleet-wide device and configuration management, documented OTA updates, staged rollouts with a clearly defined blast radius — and the ability to roll back to the last stable version at any time. That shortens MTTD/MTTR and noticeably lowers the risk of updates. Enterprise-grade observability and end-to-end APIs also mean the service slots into your existing operations and fleet processes. - Failover-ready connectivity
Real WAN bonding with robust cellular modem management across mobile and LEO satellite uplinks (Starlink, for example). That reduces dropouts, absorbs coverage fluctuations predictably, and gives you live connectivity telemetry plus secure channels for monitoring and updates. - Security and compliance by design
Operations are built around the CRA and NIS2 throughout: defined support periods and update policies, secure update processes with rollback, full visibility into software versions across the fleet, and an established vulnerability management practice (VDP, triage, advisories). Audit-ready evidence is generated automatically — which not only makes audits easier, but measurably improves service quality and security posture.
How Unwired Edge Cloud Meets the Requirements
Unwired Edge Cloud starts exactly here: a managed passenger Wi-Fi service built for the operational reality of rail fleets — with rigorous lifecycle management, enterprise observability, and resilience as a design principle.
The CRA does not only become relevant in 2027. The reporting phase in September 2026 is the next milestone, and it is close — which raises the question of whether processes, transparency, and evidence are already dependable. To support your CRA preparation, we offer a free Passenger Wi-Fi + CRA Readiness Review.
FAQ
The CRA makes passenger Wi-Fi a lifecycle topic. What counts is not just commissioning, but the ability to demonstrate security and function over years: support commitments, secure updates, structured vulnerability management, and auditable evidence.
On the operator side, that means more pressure in procurement — and clear expectations around incident readiness and fleet-wide operability.
The most pragmatic route is a managed service approach with clear operational capabilities: a complete fleet inventory (“what is running where”), OTA update processes with controlled rollouts and rollback, defined support periods with an update policy, and a dependable vulnerability process (VDP, triage, advisories).
Alongside that sit monitoring and reporting that generate evidence continuously — so compliance becomes a result of operations rather than a last-minute project.
Most faults are operational in nature: uplink instability, errors in the captive portal or authentication, configuration drift across heterogeneous fleets, no end-to-end visibility, and updates that get postponed out of risk aversion because rollback is not dependable. That produces dropped sessions and an inconsistent user experience — however good the peak bandwidth is.
WAN bonding aggregates several uplinks into one resilient overall uplink. In practice, multiple cellular connections can be used in parallel and optionally topped up with a LEO satellite link (Starlink, for example). That lowers the failure rate, makes coverage fluctuations more manageable — and makes service quality noticeably more dependable for passengers, especially on vehicles in motion.
Unwired delivers real WAN bonding as a managed service with Unwired CloudLink.
The key metrics are captive portal and authentication availability, uplink availability including degradation behavior (0/1/2 active links), MTTD/MTTR, update adoption rate and version distribution, plus utilization and headroom on uplink capacity. Combine these KPIs with live telemetry and alerts so operations spot problems before passengers feel them.
Unwired Edge Cloud comes with an extensive observability stack that keeps the metrics that matter in view.
