Skip to content
Use case 021

Railway Interlocking Workstations

A deployment concept for rail infrastructure managers, signalling vendors, maintainers and rail safety teams.

Proposed deployment · Compatibility assessment required
Rail, Aviation, Maritime and Logistics

Why this environment matters

Security for railway interlocking workstations extends beyond passwords and network firewalls. The system lets authorised staff configure, monitor and maintain logic that prevents conflicting train movements, while malicious configuration changes or compromised engineering tools could undermine route locking and signal dependencies. NØNOS could be evaluated as an execution layer that verifies software identity, limits device access and avoids unnecessary long-lived state.

The security challenge

Transport systems often operate continuously, depend on specialised protocols and must preserve safe fallback behaviour while interacting with many operators, contractors and external data sources. In railway interlocking workstations, the decisive risk is that malicious configuration changes or compromised engineering tools could undermine route locking and signal dependencies. Even strong perimeter controls may not help once authorised software, a vendor tool or a valid user session has been compromised. Internal permission boundaries must remain enforceable after initial access.

How the capsule model could help

For this system, NØNOS could run engineering, file-transfer and validation tools in separate signed capsules with no direct access to live interlocking assets unless explicitly authorised. The design would combine least-privilege device access, rapid recovery to a known state, signed operational software and compartmentalised protocol handlers. The intended result would be a set of small trust boundaries instead of one large operating environment where every service inherits broad ambient access.

Separate address spaces and capability checks can limit cross-process reach. They cannot stop harmful use of legitimate permissions, prove AI decisions correct or substitute for domain-specific safety controls.

Deployment requirements

NØNOS would need to sit beside, or be engineered into, existing certified systems without weakening deterministic behaviour, fail-safe modes, independent protection or operator procedures.

Current public-beta limitations, hardware support and application availability must be assessed before any pilot. Neither this use case nor an industry source establishes NONOS certification or a current customer deployment.

Who could buy or integrate it?

  • Rail infrastructure managers procuring engineering workstations
  • Signalling vendors integrating maintenance environments
  • Rail maintenance contractors standardising authorised service tools

Industry examples: Alstom, Siemens Mobility. Organisations shown illustrate the industry. No NONOS customer, partner or endorsement relationship is implied.

Market opportunity

Market benchmarks and device scenarios.

Published industry benchmark
US$23.64 billion

Railway signalling systems

Global · 2025 · annual market estimate

Rail signalling equipment, train-control systems and associated deployment, both trackside and onboard.

Modelled global devices
20K–400K

Candidate OS endpoints

Hypothetical planning range · 2025

Low confidence: planning assumptions. Hardware compatibility, procurement and adoption have not been validated.

Illustrative annual licensing
$3M–$280M

USD / year at full model coverage

Device scenario × assumed US$150–$700 per device / year.

Not a revenue forecast, announced price or measured serviceable market.

Device calculation

Hypothetical global planning range, 2025 scenario: assume 10,000–50,000 railway interlocking or signalling control locations × 2–8 candidate OS endpoints per site/asset = 20,000–400,000 endpoints. Counting unit: operator/engineering workstations, not safety relays. Site and asset counts, and devices per site, are planning assumptions. The installed base has not been measured. Coverage is limited to the defined equipped subset; includes all candidate endpoints within that assumed subset. Hardware eligibility, certification, adoption and achievable NØNOS share are unverified; overlaps other cases.

Railway signalling systems market report ↗

Market context only; separate from device and site population estimates. Original monetary-market scope and geography are preserved in benchmark. This source does not establish the assumed worldwide site count or endpoint density.

How to interpret the figures

Adjacent or broader commercial market benchmark; not the NØNOS OS market, licensable-device count or revenue forecast.

Modelled candidate endpoints multiplied by an assumed annual USD price per endpoint. Pricing is a planning assumption, not a vendor quote. This illustrates the full scenario range, not revenue or total addressable market. It excludes adoption timing, procurement, certification, support costs, channel economics and achievable market share. Use cases can overlap, so their totals do not represent unique devices.

Research from 2026. Publisher estimates have not been independently audited.

Read the full methodology

Explore NONOS

Choose your
NONOS experience.

Discover the platform for your organisation or explore the software.

You can reopen this chooser from the footer at any time.