Use cases
Foraging Log — where it earns its place
On Foraging Log —
Every forager has a spot they would not tell their own mother about. The Foraging Log keeps the record you would never put in a cloud account: what you found, where, when, and how sure you were — Certain, Fairly sure, or the wise old Left it alone. … On this page: three concrete ways someone whose work is measured in seasons, not sprints reaches for the Foraging Log, and the signals that tell you it fits.
When the Foraging Log earns its place
As a tracker, the Foraging Log keeps find, where — safe in this file, it never phones home, date, and confidence — no more, no less — so the record is small enough to actually read back.
Most tools in this category — farm-management SaaS, livestock-tracker platforms with per-animal pricing — solve a version of the same problem, then bill you monthly for the privilege of remembering it. The Foraging Log takes the opposite bargain: one file, once, kept.
Three scenarios drawn from outdoors, food, and hobby
The everyday one: you open the Foraging Log on a Tuesday morning, log what needs logging, and close it. Two minutes. The record is more honest than the app that pinged you to remind you.
The specific one: — the workflow it names is the record that most needs a home outside a subscription. Some people use only the Foraging Log. Some fold it into a Swiss Knife next to five others. Both are correct.
The out-of-band one: months later, you want to look back. The Foraging Log still opens because it is a file. There is no login lapsed, no export deadline missed. The record is where you left it.
Signals it fits someone whose work is measured in seasons, not sprints
You want a homestead log that behaves like a document, not a service. You are comfortable typing your own numbers in. You would rather own the file than rent the log. Weight in the knife: 1. Manual: no manual — the tool is its own instructions.
Signals it fits
- You do this kind of record-keeping more than onceThe Foraging Log pays back every time you don't have to reinvent the shape.
- You want it offline, on your own machineNo account, no cloud, no vendor between you and the record.
- You're comfortable with a hand-kept fileThe Foraging Log is a document. It behaves like one.
Questions people ask
Is it safe to write down my secret foraging spots in an app?
In this one, yes. The log is a single HTML file that runs offline in your browser, with no account and no server — your spots never leave the page and never phone home. The file is yours forever, and so is the patch.
Is this a full replacement for farm-management SaaS?
For the working core of what most people use it for — yes. For enterprise features (team seats, integrations, auto-import), no. The Foraging Log is deliberately smaller and more honest about its scope.
Who is the Foraging Log not for?
Someone whose work is measured in seasons, not sprints's opposite: a team that needs shared cloud state, or someone who wants automation over ownership. Use a SaaS for that; use this for the file.
A homestead log that opens where you left it, on the machine you left it on.