Support

Something not working?

Five things go wrong more than everything else combined, and each of them takes one line to fix. Try the one that matches your screen. If none of them do, the address at the bottom of this page reaches a person.

Try first

The five common ones

command not found: ferrow

The install worked; your terminal has not noticed it yet. Close the window, open a new one, and run it again. If it still says that, npm put the command in a folder your terminal does not search — npm prefix -g prints npm's folder, the command lives in the bin folder inside it, and adding that bin folder to your PATH is the fix.

command not found: node

Node is not installed, and Ferrow needs version 20 or newer. Install it from nodejs.org — the button marked LTS — then close the terminal, open it again, and install Ferrow:

npm install -g @ferrow/ferrow

The name is scoped — @ferrow/ferrow — but the command it installs is just ferrow. If you would rather install from a file you can check first, /download ships the same thing as a tarball with its sha256.

You paid on the website and this computer does not know

Paying and switching on a machine are two steps on purpose — nothing about your purchase reaches your laptop until you tell it to. One line does it:

ferrow activate <your key>

Your key looks like ferrow_ followed by a long string, and it is on the page you landed on after paying. The same command accepts the cs_ checkout reference or the whole web address of that page, so whatever you copied will do.

Ferrow has no completed purchase for that reference yet

Stripe's confirmation can take a few seconds to reach Ferrow. Wait a moment and run the same command again — nothing is charged twice by trying. If it has been a few minutes, that is worth an email.

You lost the key

It is still in your account. Sign in at app.ferrow.ai and open Settings → Account, where you can reveal and copy it again for a second machine. If you cannot get into the account either: open app.ferrow.ai, press Account at the top, and under the log-in form use Forgot your password? — it emails the address on the account, so check your email and follow it back in. If that email never arrives, or you have lost the mailbox too, write to us and a person will sort it out.

Then

Write to us.

One address, read by a person:

support@ferrow.ai

There is no ticket system, no bot and no phone queue. Ferrow is pre-1.0 and small, so a reply takes as long as it takes a person to get to it — usually a day or two, and longer at a weekend. We would rather say that than print a number we cannot hold to.

Four lines make almost any report answerable on the first reply:

What you ran
The command, copied exactly — including the parts you think are obvious.
What it printed
The whole message, not a summary of it. Paste it as text if you can; a screenshot is fine if you cannot.
Your machine
macOS, Windows or Linux, and what node --version prints.
If it is about money
The cs_ checkout reference, or the email address you paid with. Never send us your key, your password or your card number — we do not need any of them, and we will not ask.
If your screen does not match what we printed

That is worth reporting on its own, even when nothing is broken for you. The docs are hand-written against the real program, and every place they drift is a place the next reader gets stuck.

Also

Where the answers already are.

The walkthrough
/docs — install to first search in five minutes, with every screen Ferrow prints back shown, so you can tell whether it worked.
In the program
ferrow help prints the whole command surface, grouped. ferrow doctor checks the install and names anything it finds.
Billing and plans
/pricing for what things cost, /refunds for cancelling and getting money back.
Data questions
/privacy says exactly what leaves your machine and what does not, per surface.