Local files stay local
Grant a folder and Barie reads it in place, on the machine. Nothing is uploaded to make it readable, and the same zero-egress guarantee that covers your servers covers your laptop.
Resources · Desktop app
A native application for macOS, Windows and Linux that talks to your own Barie deployment and to nothing else. Local files stay local, the work carries on when the network does not, and there is no browser tab between you and the thing you asked for.
Reconcile the Q3 close against the folder on my desktop and flag anything that moved.
local files never left the machine0 B out
Why a desktop app at all
Most of what an analyst is holding at any moment is not in a system of record. It is a folder, a scratch workbook and three PDFs somebody sent over. The desktop app reaches those without uploading them anywhere.
Grant a folder and Barie reads it in place, on the machine. Nothing is uploaded to make it readable, and the same zero-egress guarantee that covers your servers covers your laptop.
It is your deployment behind the window, not a lighter copy of it. The same connectors, the same permissions, the same record of what was done, whichever surface you started from.
Long runs keep their state across a dropped link, a closed lid and a restart. You come back to the run you left, not to the beginning of it.
System-wide capture, a global shortcut, and a handoff into your editor for the coding agent. It behaves like an application, because it is one.
Download
Every build is code-signed and notarised, and every release publishes its checksums alongside the artefact. Deployed customers can also pull the same builds from their own internal mirror rather than from us.
Not yet deployed?The app connects to a Barie deployment and does nothing on its own. If you are still evaluating, start with a demo and we will point the app at a sandbox tenant.
Notes for IT
Specifications
See the app pointed at a deployment of your own, reading a folder that never leaves the machine.