Security and Deployment
NeoArc runs on your machine. No accounts, no telemetry, no external calls. Ships in three editions covering standard connected use, restricted networks and fully air-gapped operation.
The assumption is inverted
Most architecture tools start from the cloud. They assume a network connection, a vendor account, a subscription, and a browser tab pointed at a SaaS control plane. Working offline, when it is supported at all, is a feature bolted on to a cloud-first product.
NeoArc starts from the machine in front of you. It assumes nothing about the network. It assumes no account. It assumes no external service is reachable. Connectivity is optional and always has been. The application is the same whether the machine it runs on is on the public internet, behind a corporate proxy, or sitting in a locked room with the network card removed.
Where to go from here
If the air-gapped story is directly relevant to you, read the Defence and Air-Gapped industry page, which covers the operational detail in more depth. For the model-first story that sits alongside this one, read NeoArc Studio.
Defence, intelligence and critical national infrastructure require architecture documentation that is current, auditable, and never on a network an adversary can reach. NeoArc is built for this from the first line of code.
NeoArc Studio is an architecture workbench built around a single model. Define your domain once and every view, schema, diagram and published document derives from it automatically.