Logo
NeoArc Studio

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.

Connected
The standard deployment context. Full connectivity is available to the machine running NeoArc, and the update channel can reach the vendor directly. Suitable for teams with normal internet access and no constraints on outbound traffic.
Enterprise
Deployment into a restricted corporate network. Outbound traffic is constrained, proxies are in the way, and the organisation wants control over what NeoArc can reach. The update channel goes through a mirror you operate, so no direct vendor connection is required.
Sovereign
Fully air-gapped operation. No network path to the outside world and no expectation that one exists. Updates arrive on verified media and are installed manually. The product has no external touchpoint at any point in its lifecycle.

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.