In practice

The same software, and a genuinely different product each time

Filamental bends further than one description can carry. For one user it is a filing cabinet that finally makes sense, for another a case file that can be handed over, for another the only place a whole network can exist at once.

So we write these pages as we hear about who is using what and where. Feel free to chime in and tell us, we don’t collect user data so we rely on your emails to provide feedback.

Academia and research

See the objection before the reviewer does

For principal investigators and research fellows. A grant case is assembled out of a literature review, a dataset, a model configuration and a partner institution, and the first person to read it whole is the reviewer looking for what is wrong with it.

Read it →

AI engineering

Find out what actually changed between v3 and v4

For applied machine learning teams. Your tracker holds the runs and your registry holds the versions. Neither holds what an experiment settled, which corpus a relabelling pass touched, or what the eval set was never covering.

Read it →

Authors

The second job nobody warned you about

For the novelist eleven months into a draft, when keeping track of who knows what has quietly become a job of its own. The cast, the threads and the promises made to a reader, held so the unfinished ones show up on their own.

Read it →

Campaign execution

Move the launch date and see exactly what it breaks

For whoever owns the whole of a campaign running across many markets and many workstreams: production, freight, install, creative sign-off, retailer approvals, digital integration, support. Part proposal, part plan, part reference, out of one structure.

Read it →

Construction and development

Every condition, and the thing it is holding up

For small residential developers. The pre-commencement condition, the drawdown that unlocks on evidence of start on site, and the contribution that falls due on first occupation. None of it has a date, and all of it is load-bearing.

Read it →

Consulting

Hand over the model, not just the recommendation

For independent consultants and small practices. Two weeks in you hold a working model of how the client actually operates, and it is the one thing that never gets delivered. Here it can be, and where the leverage sits turns out to be a shape.

Read it →

Creators

You are running a production company now

For the person whose channel grew an operation around it. Locations that need permission, people who have said things on camera, a sponsor owed a deliverable by a date, and a back catalogue too large to hold in your head.

Read it →

Datarooms

Every open item, what it costs, and what it is blocking

For the sell side of a raise or an exit. Your data room holds the documents; this holds the dozen findings that decide the deal, each carrying what it is worth, the contract it came out of and the decision it is holding up.

Read it →

Farming

Every document about that field, attached to the field

The soil survey, the drainage invoice, the spray recommendation, the photos from the wet corner. Drag them onto the field they belong to and that is where they stay. A fifteen year old farm office drive stops being where things go to be lost.

Read it →

Investigations

The link chart that is never out of date

For compliance analysts, journalists, fraud and asset tracing. You record what you found and what it connects to, the chart assembles itself from that, and every line traces back to the document that put it there.

Read it →

IT and networks

Trace the outage back to the decision that caused it

For the one or two people who run an estate on their own. Monitoring tells you what is down and the ticket tells you what a user noticed. Neither tells you that the array was sized in 2024 against a forecast nobody wrote down.

Read it →

Software teams

Why it is built this way, and what you rejected

For engineers who have watched three wikis die. The repository is a complete account of what the system does and a total blank on what was considered and discarded, which is the part that costs six weeks when somebody leaves.

Read it →

Startup founders

Answer the diligence question once, not four times

For founders raising a seed or a Series A. The pipeline is in a spreadsheet, the answers are in email and the grant deadlines are in a portal, so the only thing joining them is you, and two funds have just asked the same question in different words.

Read it →
Or skip the reading

Create a folder and drop in some files, add notes, join them together

Free permanently, no account, no card, and nothing to cancel if it turns out it is not for you.

Version
0.3.40
Platforms
Win / macOS / Linux
Personal
Free, permanent
Professional
$120 / year
Where does this go?

You know that feeling when something new turns up and the first thing you have to do is decide where to hide it

A new case, a new client, a new scheme, a new season. It arrives as a handful of things that obviously belong together, and before you can do anything useful with any of it you have to answer a question you cannot possibly answer yet. Where does this go? So you guess, and the guess becomes the anchor.

Six weeks later the work has moved in a direction nobody expected, and the folder it lives in is a record of what you thought on day one. Nothing is lost, exactly. It is just out of sight, and out of sight is indistinguishable from gone for anything you had not already decided mattered.

Filing is what you do once you know. Everything above is about the stretch before that, which looks nothing alike from one kind of work to the next. The whole argument is set out here.