Ferrow · in development · Ruzylo Holdings · Thousand Oaks, California
Ferrow is a local-first knowledge system with agents inside it. Your notes, your files, your projects — and the workers that act on them — running on your own machine. An operating system for one person’s thinking, that you own rather than rent.
Read this before anything else. Ferrow is early. There are no screenshots on this page because there is nothing yet to photograph, no feature list presented as shipping, and no date. What follows is the philosophy, the category, and the honest origin — stated plainly so you can decide whether it is worth watching.
01 — The category
Design intent, written before the build. Nothing in this section is claimed as shipping.
A vault remembers and does nothing. A chat window does something and remembers nothing. Ferrow is the third thing: a store of your own knowledge that can be put to work, on the machine where it already lives.
Plain files in a folder you can open without us. Your writing, your references, your project history — structured enough for a machine to reason over, ordinary enough that a text editor still reads them in ten years.
The format is the durability guarantee. A knowledge base you can only read through one company’s software is that company’s knowledge base.
Intended · your disk · open formats · no lock-in ritual
A note that describes a job is a job. Write down how something should be done, point it at the part of the vault it concerns, and it becomes a standing worker — researching, drafting, checking, filing — against your material rather than against the open internet.
This is the line between a second brain and an operating system: one holds what you know, the other acts on it while you are doing something else.
Intended · notes as instructions · agents with context
Whatever the system produces lands in the vault as another file you own — a draft, a report, a decision with its reasoning attached. The loop closes. Nothing useful is stranded in a transcript.
Output that cannot be filed is output you will lose. Ferrow treats every result as a document, not a message.
Intended · results as artifacts · one place, always
The system, the vault and the work all sit on your hardware. You may point it at whatever intelligence you choose — that is your decision and your account — but nothing about your own knowledge requires somebody else’s server to be reachable.
Offline is not a degraded mode. It is the ordinary case, and everything else is an option you switched on.
Intended · local-first · your machine is the server
02 — The position
These are settled. They were settled before the product had a name, and they constrain everything after.
Everything you have written down, collected and worked out is the most personal thing you own. It should sit on hardware you can unplug. Not synced by default, not held in trust, not one policy revision away from being somebody else’s corpus.
A system built this way is slower to make and harder to monetize. That is the trade, and we are making it deliberately.
A privacy policy is a promise, and promises get revised, acquired and subpoenaed. Architecture is different: a system that never received your data cannot be compelled to produce it, cannot leak it, and cannot quietly start training on it after a funding round.
The test we hold ourselves to is simple — if the honest answer requires the words “we would never”, the design is wrong.
The bar · no telemetry required to use it · no account required to open your own vault
The workers you build up over months — the ones that know your standards, your clients, your file conventions — are as much your property as the notes they read. They should be files you can copy to another machine, inspect, edit and keep.
An agent you rent stops working the day the rent stops, or the day its terms change. That is not a tool. That is access.
Open, readable formats. No export ritual, because there is nothing to export — the files are already on your disk in the shape you would want them. Leaving should cost you nothing but the software.
Software that is hard to leave eventually stops trying to be worth staying for.
A tool that runs on your own machine, using your own compute, should not bill you monthly for the privilege. We prefer software you purchase and then own, the way you owned software before the meter arrived.
Pricing is not decided and we will not pretend otherwise. The direction is: a stated bias, not a published price.
Undecided · stated as intent · no price published
03 — The name
Two words held in one, and a mark that admits the work is unfinished.
The planner’s line. The straight cut a plough draws to turn open ground into a worked field — the oldest evidence that somebody decided what this ground was for.
The one walking it with you. Not an assistant standing by for instructions; something that already knows the field and keeps pace along it.
The mark is that field seen from directly above: two arcs crossing to make a strip, seven chords lying across it, each as long as the strip is wide at that height. The center chord does not stop at the edge. It carries past the field and ends in the open.
That overrun is the whole idea. The field is the work that got done; the line leaving it is the one still being drawn. We chose the mark before the product existed, and it says so out loud.
04 — Provenance
The part of this page that is entirely a matter of record.
Built because the founder needed it. Productized because it works.
Ferrow is not a category study that turned into a company. It descends from a private system its founder built for himself and still runs his entire company family on — the ventures, the operations, the calendar, the code that gets reviewed and the work that gets shipped. That system was never intended to be a product. It was intended to be enough.
It has run daily, on his own machines, for long enough that the argument for local-first stopped being philosophical. When the network is out, the work continues. When a vendor changes its terms, nothing on the disk changes. When a question needs an answer from four years of accumulated context, the context is there, because it never went anywhere.
Ferrow is the deliberate act of taking that instrument, drawing its edges properly, and making it something another person could own. Ruzylo Holdings is doing the work. It is early, and the honest description of where it stands is written above.
The private system is not shown here and never will be — it holds a working company’s real material. That is the same standard Ferrow is being built to.
05 — Constraints
Easier to verify than a feature list, and harder to walk back.
Opening, searching and working your own material is a local operation. If our servers vanished tomorrow, your vault would open tomorrow.
Your notes are not a dataset. They are not a case study, a screenshot in a deck, or a sample in a demo.
Readable formats on your disk. The value has to come from what the system does with them, not from being the only thing that can open them.
No countdown, no fake beta, no waitlist counter. When a date exists it appears on this page, and not before.
On the things not listed here
Plenty is undecided — the exact shape of the agent model, which local engines are supported first, whether any part of it is opened up, what it costs. We would rather say “undecided” four times on one page than publish a plan we already know will move.
06 — State
Three states carry color in this system: working, done, and stopped. Nothing here is dressed as further along than it is.
There is no roadmap on this page. A roadmap with invented dates is a marketing document, and the rows above would all be one row further along if we were writing one. The idle rows do not animate, because nothing is happening on them yet — a system that fidgets while idle is lying about its state.
07 — Answers
Including the ones that are simply “no” and “we do not know yet”.
No. There is no build, no installer and no early binary. Anything claiming to be Ferrow today is not.
No date is set. The specification is being written; the build has not started. Any date given now would be a guess dressed as a commitment, and it would be wrong.
When a date exists it will appear in the status strip at the top of this page.
Undecided. The bias of the house is that you buy it once and own it — the software runs on your machine and your compute, so a monthly meter is hard to justify. That is a stated preference, not a published price.
Undecided
Not to open, search or work your own vault. That is the architectural commitment, and it is the reason the project exists.
If you choose to point it at a hosted model, that call goes where you send it, under your account, on your decision. Choosing to reach out is not the same as being required to.
Undecided. What is decided is the part that protects you either way: the vault formats will be open and documented, so your knowledge is readable without our software regardless of how the software itself is licensed.
Undecided
A notes app stores; a chat window converses. Ferrow is being designed so that written knowledge becomes standing work — a note describing a job becomes a worker that does it, against your material, and files the result back into the same vault.
Whether that lands as designed is exactly what the build will decide. It is stated here as intent.
Ruzylo Holdings, of Thousand Oaks, California. Ferrow descends from the private system its founder built for himself and runs his companies on. Small, self-directed, and answerable to nobody who would ask it to add telemetry.
Not yet — there is nothing to try. Write to us and you will hear directly when a private trial exists. There is no queue to join and no position to hold.
08 — Interest
No form on this page, no signup, no tracker, no counter ticking upward to look like momentum. Write to us and a person answers. You will hear when there is something real — a build, a trial, a date — and nothing in between.
Write to
hello@ardenholt.com