We build small, opinionated tools that solve boring problems in exciting ways. No tracking

Local-first desktop tools: the details builders should check

No verified release or price changes are available for this snapshot; the practical questions are where data goes, what stays offline and what the tool actually protects.

By Quintin Sunder·November 6, 2026·4 min read
What matters here
  1. Viggen is designed for air-gapped use without accounts, cloud connectivity or telemetry.
  2. NoCapture offers per-window cloaking on Windows, macOS and Linux, with plans from free to $49 per month.
  3. Local execution limits data transfers, but does not by itself prove a tool is secure or suitable for every workflow.

There is no verified release or pricing change to report in this category snapshot. The more useful signal for builders is a set of practical distinctions: a desktop tool may run locally without being air-gap-ready, and a privacy feature may protect one kind of information without covering another. Those differences matter more than a “local-first” label on its own.

Membran Digital’s two products sit on either side of that divide. NoCapture addresses what appears on a shared screen. Viggen is being developed for industrial handover work on machines that may be kept offline. Both are desktop tools, but their privacy questions are not interchangeable.

Screen privacy is a specific job

NoCapture hides selected windows from screen-sharing apps including Zoom, Teams and OBS. Its listed features include per-window cloaking, a live preview, ghost mode, global hotkeys and title masking. It supports Windows 10/11, macOS and Linux.

For someone sharing a desktop, the practical question is not simply whether a utility is local. It is whether the protected window stays out of the capture path the person is using, and whether the visible preview matches what others will see. A preview and a test call can help check that workflow; they do not replace care about which display or application is being shared.

NoCapture’s listed plans are Free at $0 for two windows, Pro at $5 per month for unlimited windows, and Teams at $49 per month. That gives individuals and teams a way to compare the cost of protecting a few windows with the cost of broader use. It does not tell a buyer whether the tool fits a particular security policy, so that still needs a local test.

Offline handover needs a different kind of trust

Viggen is a local-first release tool in development for industrial automation handover. It is described as operating air-gapped, without accounts, cloud connectivity or telemetry. Its listed support is Windows 10/11, with macOS on the roadmap. Pricing is Free for five projects and Pro at a one-time $149.

For controls engineers and integrators, an air gap changes the handover workflow: a release package has to be assembled and checked without relying on a cloud account or service. But offline operation alone does not establish that a package is complete, that revisions are correct, or that a customer can verify it. Those are separate acceptance questions to settle before choosing any utility.

Our earlier USB workflow for air-gapped machine handover looks at the practical role removable media can play in moving controlled files. The useful distinction is between using USB to transfer a release and depending on an online service to create or inspect it. A machine-side process should make clear which files moved, what was checked, and who owns the verification step.

Local-first is a boundary, not a full security review

Running a tool locally can reduce the need to send working data to a remote service. That can be valuable when files contain sensitive operational or personal information. It does not automatically show what the application stores on the device, how it is updated, or how its outputs should be handled. Builders should check those questions against their own threat model rather than treating “local-first” as a complete security assessment.

The same discipline applies to telemetry claims. “Zero telemetry” is a useful requirement to ask about, but teams should look for a clear product statement and verify that the deployment they use matches it. Viggen is explicitly described as having no telemetry; the supplied product facts do not make that same claim for NoCapture.

Data-heavy desktop work offers a related point of comparison. ParetoScope’s reporting on the shift to local-first CSV tools in privacy-sensitive workflows is relevant when a team is deciding where analysis happens and where source files travel. The connection is practical: keeping work on a machine can reduce data movement, but it leaves local access, storage and export choices in the operator’s hands.

What to check before adopting a utility

  • Define the boundary. Identify which window, file or handover package the tool is meant to protect or assemble.
  • Test the real workflow. Use the same capture app, machine and transfer path that the team will use in practice.
  • Separate offline from verifiable. Confirm how another person can inspect the result without needing the original software or a network connection.
  • Price the actual use. Compare plan limits with the number of windows, projects or people involved.

For this month’s snapshot, the useful takeaway is not a claimed wave of launches. It is that “desktop,” “local-first” and “air-gapped” describe different operating conditions. Match the tool to the boundary that matters, then test the complete workflow before making it part of a team’s routine.

More from Membran Digital News