Security & Deployment
Your Data Never Leaves Your Network
Everything a security reviewer normally asks, in one place — so an evaluation does not stall waiting on answers.
Your process data never leaves your network.
ReliaSim is desktop-native by design. In a market rushing to move everything to the cloud, we built ReliaSim for the reality of modern manufacturing: segmented networks, isolated OT environments, and IP that should never have left the plant in the first place.
Install and run. No procurement cycle.
No SaaS vendor approval. No security review queue. No waiting on IT to greenlight a new cloud service. Download the installer, open your model, simulate in minutes.
No outbound data flow. Air-gap compatible.
Runs entirely on the user's machine, inside your firewall. No cloud uploads, no third-party data processor agreements, no exfiltration risk. Operates in physically or logically isolated networks — only license and version checks touch the internet, and even those can be deferred.
Your IP stays on-premises.
Your simulation models encode proprietary process knowledge — that's trade-secret territory. Keeping it local removes an entire class of vendor risk and shortens compliance review. Friendly to ITAR-, CMMC-, and GxP-bound deployments.
Common questions from IT and security reviewers
No. After install and license activation, ReliaSim runs entirely offline. The application makes no outbound calls to load data, run simulations, or persist results. Periodic license and version checks occur over HTTPS when a connection is available; these can be deferred for air-gapped deployments.
Yes. ReliaSim is compatible with air-gapped (physically or logically isolated) networks, including OT segments, defense facilities, and validated GxP environments. Offline licensing is available for installations that never touch the internet.
On the user's machine, in locations the user controls. Models, input data (CSV / historian extracts), and simulation results are read from and written to local files. ReliaSim has no cloud datastore, no telemetry of model contents, and no third-party data processor.
No — and that is deliberate. Manufacturing process knowledge is trade-secret IP, and the operating environment of our buyers is segmented networks. We will not ship a SaaS version that compromises that. Need to share results across a team? You share files, not data exposure.
The MCP server is local. It exposes your model to whichever AI assistant you point at it — and you control that choice. If you connect to a hosted assistant, the data your assistant sees is governed by that assistant's policy. If you connect to a local model, nothing leaves the machine. The choice is yours, not ours.