Faraday Web Demo

The demo is deliberately honest about its boundary

A public browser link cannot demonstrate a machine that has been physically disconnected from the internet. Faraday Web makes that distinction explicit. Its Windows-style desktop and workbench are interactive, but the deployed version uses hosted open-weight models through external APIs so visitors can try the flow without installing a local model runtime.

That distinction matters because a polished interface can make a security claim feel stronger than the architecture behind it. The project labels the hosted path as a simulation and points people to the companion Faraday repository for the on-device version. A demo becomes more useful when it describes what it can and cannot prove.

A workstation metaphor makes the workflow legible

The interface is built as a simulated operating-system desktop with a window manager, taskbar, start menu, virtual file system, file explorer, notepad, terminal, browser and settings. Faraday appears inside that environment as an application rather than as a disconnected chat box.

The public version also exposes interaction paths for model routing, image attachments, code work and document delivery. Tool calls can be shown in the simulated terminal or browser. That gives a visitor a way to inspect the sequence of work, not only the final answer.

• The real local product is in the Faraday repository and uses local open-weight models on the operator’s hardware.
• The browser deployment is a hosted demo. It is not an air-gap and should not receive confidential files.

What this demo proves, and what it does not

The shared router, egress controls and document-generation paths make this a useful interface and workflow demonstration. The browser version can help people understand how the product is supposed to feel and where evidence or control appears in the workflow.

It cannot prove that the visitor’s data stays on their own computer, because requests made by the hosted version leave the browser and reach the model providers. For a real privacy assessment, the local deployment, network boundary, model configuration and audit trail all need to be checked on the target machine.