Download — Ferrow

The one line

Any machine with Node 20.

This installs the ferrow command globally, from the npm registry. macOS, Windows and Linux, the same line on each.

npm install -g @ferrow/ferrow

The name is scoped — @ferrow/ferrow — because npm reserves bare names that look like existing packages. The command it installs is still just ferrow. Prefer a file you can check first? The same thing ships as a tarball with its sha256 published below, and npm install -g https://ferrow.ai/dl/ferrow.tgz installs it identically.

Then, in order:

ferrow                   # tells you what is connected and what is next
ferrow detect            # or: ferrow connect openai
ferrow vault init
ferrow note inbox/today.md "the thing I just learned"

Bought Ferrow on the website? One more line switches this machine on — ferrow activate <your key>, using the key from the page you landed on after paying. It also takes the cs_ checkout reference or that page's whole address.

Never used a terminal on purpose? The five-minute walkthrough shows every screen Ferrow prints back, so you can tell whether it worked.

Terminal-first

Bring your own agent.

The ferrow command is not a companion to the app. It is the product, headless: the vault, the memory, the skills, the capability contracts, the change log, the schedules, the kill switch. Everything the desktop app can do starts here, and a few things only live here.

So if you already work inside Claude Code or another terminal agent, you do not have to switch to anything. Two ways to use that:

1. Let your agent do the setup. Ferrow ships a setup contract: one prompt you paste into your own agent, where every step carries the command, the output that means it worked, and what to do when it does not. It stops and asks you before anything that needs a key, and it never turns on writes by itself.

ferrow help              # every verb, with what it costs you

The prompt to paste is SETUP-VIA-AGENT.md, published right here. It is a text block, not a script: you can read the whole thing before your agent runs a line of it. Stuck anyway? /support answers by email.

2. Make Ferrow your agent's memory. Ferrow speaks MCP in both directions. It can call other people's servers, and it can be one: point your agent at ferrow serve-mcp and your vault becomes searchable and readable from inside the tool you already use.

claude mcp add ferrow -- ferrow serve-mcp   # Claude Code
ferrow serve-mcp --check                    # what would be exposed, without serving

Any MCP client works, not only that one: {"mcpServers":{"ferrow":{"command":"ferrow","args":["serve-mcp"]}}}

What it exposes, and what it refuses

Reading and searching your notes and your memory are on. Writing, and running your skills, are off until you say otherwise in ~/.ferrow/serve-mcp.json, and a refusal names that file and the one line that changes it. When you do turn writing on, every write goes through the change log attributed to the client that made it, so ferrow log shows it and ferrow log revert undoes it. A skill run this way stays inside its own capability contract: reaching Ferrow over MCP grants nothing that running it yourself would not.

Desktop builds

A window instead of a prompt.

These are pre-1.0 and not code-signed yet. macOS will say the developer cannot be verified and Windows will show a SmartScreen warning. That is what an unsigned build looks like; the signing certificates are bought and installed by a human, and that has not happened yet. If that warning is not something you want to click through, use the terminal route above, which has nothing to sign.

macOS

Ferrow.dmg — Apple silicon and Intel in one image, 2.7MB. The next release splits this into two smaller per-arch builds — arm64 and Intel — each listed here with its own hash when the files exist.
8d0c71f88ec4cc251e8a8ed815d1dd96026901663d56d68adfe0c679d2a5a56a

Windows

Ferrow-setup.exe — x64 installer, 1.1MB.
8671927c5d958a488fa21a7a7be22fe5948ba0e6ffabee65ee2a6bc74c595fb4

Linux

Ferrow.deb — amd64, for Debian and Ubuntu, 1.4MB.
3fb364966ce6ba9754467fc14108ed7534daa3c62b67feee58403511f84aa643
No AppImage here yet — on Linux it is the .deb or the terminal route.

The tarball

ferrow.tgz — the same package the one-liner installs from the registry, as a file you can check first. v0.1.6, 0.9MB, 188 files. CI stamps ferrow.tgz.sha256 beside it on every repack.
4533e4afc5d339afff1fe0996f0751d1b9ac5ed7d36e74da4060b0ff9c826769

Check any of them before you open it:

shasum -a 256 Ferrow.dmg        # macOS and Linux
certutil -hashfile Ferrow-setup.exe SHA256   # Windows

Each prints one long string of letters and numbers. It must match the one printed beside that file above, character for character — if it does, the file you have is the file we built.

No install at all

Use it in the browser.

The web client at app.ferrow.ai is the same interface with nothing to download. It holds no vault of its own: you pair it with a hub you are running (ferrow hub start), and it reaches that machine through a relay that carries sealed blobs it cannot read. Your notes stay where they already are.

Which one do I want

If you are trying Ferrow for the first time, the one line at the top of this page is the shortest path to a working vault. The browser client is worth it once you want the same vault from a machine that is not yours.

Phones

Not yet, honestly.

Android

Builds, unsigned beta. The AAB comes out of CI; it is not signed for the Play Store yet.

iOS

TestFlight soon. The build pipeline exists; the app has not gone out to testers yet.

In the meantime app.ferrow.ai works in a phone browser against your own hub.

The walkthrough shows every screen Ferrow prints back, so you can tell whether each step worked. On your own machine and your own keys it is free; pricing is what Ferrow's own side of it costs.

The five-minute walkthrough Pricing