Security & Deployment
Your Data Never Leaves Your Network

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.

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.

Not if you do not want it to. The add-on speaks MCP, so it works with any MCP-compatible assistant — including models running locally on your own hardware, such as Gemma. In that configuration the assistant, the model and your data all stay inside your network, and the air-gap holds.

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.

New releases are announced, and you install them on your own schedule. Updates are not pushed to the modeler's machine, so nothing changes in the middle of quarter-end.

A model is a file. Wherever your laptops and desktops are already backed up, the model is backed up too, and there is no separate backup system to integrate. Data residency works the same way, because the model sits wherever the machine already complies.

Through the tools you already operate, such as Git, OneDrive, SharePoint or a shared drive. Models are shared as files, not through a vendor account.

The work is recoverable. Models live in files you control, so the standard handoff applies, and the license is re-issued to the replacement modeler.

No. The website and the Sandbox are marketing surfaces that run demos on sample data. The product is desktop software that runs offline on the modeler's machine.

Yes. ChiAha has signed the standard agreements at large enterprises. For a specific compliance regime, such as a regulated industry or a restricted network, a call is the quickest way to work through the details.