Architecture documentation for air-gapped environments
NeoArc is designed for environments where external connectivity cannot be assumed. Air-gap is not a configuration option. It is a structural property of how the tool works.
Most architecture tools assume the internet. They assume a user account, a licence check, a telemetry endpoint, and a cloud store for files. A product built on those assumptions is not air-gap-ready. It is cloud-dependent with offline degradation, and the degradation is usually severe.
NeoArc inverts the assumption. It is built for air-gap first. Connectivity is optional, not structural. Every feature in the product runs locally, because there was never a cloud service on the other side of it.
If you want the technical detail on the security posture and deployment model, see security and deployment. For the industry view of how this lands in defence and sovereign environments, see defence and air-gapped.
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.
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.