Skip to content
Use case 069

Refinery Process Historian Gateways

A deployment concept for refineries, petrochemical companies, OT security teams and process engineers.

Proposed deployment · Compatibility assessment required
Energy, Utilities and Resources

Why this environment matters

Security for refinery process historian gateways extends beyond passwords and network firewalls. The system collects high-volume plant data for analysis, reporting and engineering review, while a historian compromise can alter operational evidence, expose proprietary process information or become a bridge between business and control networks. 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

Energy and resource systems combine high-energy equipment, geographically distributed assets and operational technology that cannot be patched or restarted like an ordinary office computer. In refinery process historian gateways, the decisive risk is that a historian compromise can alter operational evidence, expose proprietary process information or become a bridge between business and control networks. 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 use one-way or tightly scoped ingestion capsules, signed connectors and isolated analytics without broad control-network credentials. The design would combine zone-specific capabilities, isolated remote maintenance, minimal persistent administration state and a verified boot chain. 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

Deployment would require site-specific engineering, segregation from independent protection systems, deterministic performance testing, change control and compliance review. NØNOS would not replace certified relays or safety systems by default.

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?

  • Refinery operators buying data-integration and historian upgrades
  • Historian software vendors qualifying secure collectors and connectors
  • OT integration firms implementing refinery-to-enterprise data interfaces

Industry examples: AspenTech, AVEVA. 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$1.32 billion

Data historians

Global · 2023 · annual market estimate

Historian software and associated services across industries; refinery gateways are a subset.

Modelled global devices
2.5K–45K

Candidate OS endpoints

Hypothetical planning range · 2025

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

Illustrative annual licensing
$375K–$27M

USD / year at full model coverage

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

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

Device calculation

Hypothetical global planning range, 2025 scenario: assume 500–1,500 oil refineries and refinery-like processing complexes × 5–30 candidate OS endpoints per site/asset = 2,500–45,000 endpoints. Counting unit: historian/security gateways between process and enterprise networks. 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.

Data Historian Market Size, Share, Growth 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.