Ferrow Overview Pricing Docs
Pricing

Two editions. One number each.

The difference between them is who holds the API accounts. Everything else — the vault, memory, agents, skills, the Council, projects, import, the local UI — is the same product on both.

The two
Private

You bring the keys

$20 / month
or $180 a year — twelve months for nine.
Models
Your own API keys, or a model running on your own machine. Stored in your keychain.
Usage cost
Whatever your provider charges you. Ferrow never sees that bill and takes no cut of it.
Trial
3 days, free. Cancel inside it with ferrow unsubscribe and you are charged nothing.
Managed

Ferrow holds them

$20 / month + usage
Same subscription. Usage on top, itemized.
Models
Prebuilt and billed through Ferrow — no provider accounts to open, no five dashboards to keep.
Usage cost
Provider cost + 15%, itemized per call. The margin is the whole business model and it is written on the page rather than folded into a "credit".
Cap
A hard stop you set. ferrow spendcap 50. Ferrow does not charge past it.
Trial
None — Managed spends real money on your behalf from the first call, so a free trial would be us giving away someone else's compute.
Start

Subscribing is two commands.

npm install -g ferrow
ferrow subscribe monthly     # or: yearly, or add --managed

The npm package is not published yet — that is the last step before launch, and this line starts working the moment it lands.

Ferrow prints the checkout link and does not open your browser. You should see where you are being sent before you get there. After you pay, ferrow billing activates that machine.

The cap is a stop, not an alert

On Managed, set the number before you spend anything: ferrow spendcap 50. ferrow spendcap status shows the cap, what has been spent, and what is left. There is no overage line on your bill, because there is no overage.

Questions
What actually leaves my machine?

Your prompt goes to the model provider you connected — on Private, that is your own account; on Managed, it is Ferrow's. That is the only outbound call the CLI makes.

Billing talks to Stripe, which sees a subscription id and an email and never sees a vault. If you turn on the relay so your phone or a browser can reach your hub, it carries end-to-end-encrypted payloads between your own devices and cannot read them.

Your notes do not leave. Your API keys do not leave. There is no telemetry and no analytics on this site or in the CLI.

What does Managed actually cost me?

The subscription, plus whatever the underlying provider charged for your calls, plus 15% of that. Itemized, so you can check the arithmetic against the provider's own published rates.

The number that decides your bill is the cap, and you set it. Ferrow stops there. If you never set one it uses a conservative default — ferrow spendcap status tells you what it is before you spend anything.

How do I cancel?

ferrow unsubscribe. That is the entire flow. No confirmation maze, no discount offer, no exit survey.

It tells you the date your plan ends. You keep everything you paid for until then, and nothing else is charged. Your vault and your notes were never ours — they are files on your disk and they stay exactly where they are.

Do I need to pay at all?

The vault, memory, search, undo, skills, the Council, projects, import and the local UI all run against a model you connect yourself. There is no account to create before Ferrow works, and nothing is uploaded.

The subscription pays for the orchestration layer, and on Managed for not having to hold five API accounts. If that is not worth $20 to you, say so in an issue — that is a more useful sentence than a lost sale.

Monthly or yearly?

$20 a month, or $180 for a year — twelve months for the price of nine. Ferrow is pre-1.0 and has not had its first outside user, so the honest advice is to start monthly and switch when you are sure.

Can I switch between Private and Managed?

Yes — ferrow subscribe monthly --managed starts a Managed plan, and dropping the flag starts a Private one. A new checkout is a new subscription, so cancel the old one with ferrow unsubscribe first.

Which is this, live or test?

Live, always, unless you pass --test. The CLI will not quietly put you in test mode: somebody typing ferrow subscribe means to subscribe, and a command that took their time for nothing would be its own kind of lie.