Standby keeps the replacement ready. Fabric keeps the settings and shows you what is on the floor. Endpoint keeps the operating PCs patched on your schedule. Take one or take all three. You never pay twice for the same capability. Scope: OT and its supporting infrastructure, within an agreed site scope.
The Surya platforms
Three platforms. One operating standard.
Standby keeps the replacement ready. Fabric keeps the settings and shows you what is on the floor. Endpoint keeps the operating PCs patched on your schedule. Take one or take all three. You never pay twice for the same capability.
01
Physical readiness and supply chain
Surya Standby
The spare is built, checked and waiting before anything fails. Operator stations, workstations, switches, firewalls. In a locker or a locked cage at your site, restocked from Research Triangle Park.
Prepare supported station and network replacements to approved configurations
On-site lockers or secured rooms and cages suited to the equipment
The Windows PCs that run the work. Inventoried, checked against the configuration you approved, patched in your window. Nothing lands on them that you did not sign off.
Check supported Windows inventory
Check approved configurations and record differences
Deploy approved packages and patches in maintenance windows
OT separated by default. Air-gapped where required. Connected only through controlled interfaces.
This is the condition of entry. Your network owner builds and runs the separation. We work inside it, connected or fully offline.
Minimum standard
The baseline at every site
OT in its own zone, apart from corporate IT
No flat network and no shared trust between office and floor
Nothing crosses unless it is documented and approved
Secure IT/OT convergence
Segmented and connected
Traffic crosses only where your network owner has opened a path. Our remote engineers use those paths and no others.
Where the site requires it
Air-gapped
No live path to corporate IT, the internet or the cloud. Work happens on site. Updates arrive by an offline transfer you approve.
What each profile does and does not mean
Segmented and connected: Explicitly authorized network traffic and vendor access.
Segmented and connected: Remote engineers configure and monitor only through approved access paths within the agreed boundary.
Segmented and connected: The designated network owner controls approved interfaces; application integration stays with system owners.
Air-gapped: Operation, administration and approved automation run locally.
Air-gapped: Information and packages move through customer-approved offline transfers.
Air-gapped: Changes and monitoring execute locally, with no live remote connection.
Air-gapped: Qualification names a local execution and monitoring owner, who carries out offline transfers, the review schedule and the exception handoff.
Blocked internet access alone is not an air gap, and an air-gapped site does not also have live IT/OT connectivity. Remote access paths are not part of the air-gapped profile.
Air-gapped equipment has no remote real-time monitoring; local checks are reviewed on the agreed schedule. Working through an internet outage is not the same as an air gap.
Disconnected operation is confirmed only after supported components, versions, local administration, application and identity dependencies, and offline transfers are qualified. On-premises deployment alone does not establish air-gap capability.
Industries
One standard. Two kinds of site.
Production continuity
Manufacturing
The spare is three days out. The last good program is on a laptop that left with the integrator. Surya is how a plant stops living that way.
The replacements and the supply chain behind them. The configuration backups. The OT inventory. The operating PCs.
Your IT team or MSP
Email, identity, business applications, employee laptops, and the network. Not our business, and we will not quote it.
Plant engineering, clinical engineering and your OEMs
The process, the logic, the calibration, and the call on return to service. Always.
How an asset comes into scope
An asset comes into scope when it supports the site's production or care delivery and matches a supported Surya configuration. Changes to running equipment follow the designated owner's approvals and the agreed maintenance and change process. Network ownership is named at qualification; platform visibility does not transfer network enforcement or operation to Surya.
Your next step
We do not take every site.
Tell us what yours runs on. If we can stand behind it, you get a scope and a clear line on who owns what. If we cannot, we will say so.