You started because you wanted to make the thing. Somewhere between the fourth video and the four hundredth, an operation grew around you: locations that need permission, people who have said things on camera, sponsors owed a deliverable by a date, and a back catalogue too large to hold in your head. Nobody hired you to run it and nobody handed you anything to run it with.
Four locations, two of which need permission and one of which you can only get on a Tuesday. A contributor who has appeared before and said something you are about to contradict in the film you are cutting this week. Three edits in flight. A sponsor integration that has to go out before the end of the month, in a video that is not finished. Twenty-two minutes of drone footage you know you shot for something and cannot place.
And a back catalogue large enough that you genuinely cannot remember whether you have already covered this, or how many times you have circled it and stopped.
None of that is the craft, and all of it is now your job. It fails quietly: a permission lapses without anybody noticing, a topic gets attempted for the fourth time by somebody who has forgotten the first three, a person on screen contradicts themselves and a comment section finds it before you do. Not because you are disorganised, but because you have been asked to hold a web in a format that only does lines.
A contributor is not a name in three call sheets. A location is not a line in an old email. Here each one is a single object you can open, and everything it touches is listed on it: every video it appears in, every permission it needs, every obligation attached to it, every piece of footage that came out of it. You write the connection once, when you notice it, and it is there for the rest of the channel's life.
What that buys you is the ability to see a problem in its shape. A person who has been on camera twice is one node with two videos hanging off it, so two incompatible things they have said sit side by side rather than eighteen months apart. A scripted video whose location permission has expired is a film pointing at a permission marked lapsed. A topic circled four times is a topic with four videos on it, in order, with a note on each one about what it failed to do.
And you can put the actual material on it. Drag the release form onto the contributor, the permit PDF onto the location, the contract onto the sponsor, the raw drone clip onto the shoot it came from, and they sit there and open in whatever normally opens them. The research does not go into a folder named after the month you did it.
Load Bearing is an invented channel about infrastructure and how things get built. Nine videos, four topics, four contributors, four locations, three sponsor obligations and the footage. It is not a content calendar and there are no dates in it beyond the ones that are genuinely contractual. It is what the channel is made of.
The topic that took four goes. Concrete has four videos attached to it: one that tried to do chemistry, history and carbon at once and did none of them, one that glanced off it, one in the edit, and the one that finally landed by doing only the carbon argument through one foundry and one person. Held as a topic rather than a tag, the four sit in order with a note on each about what it failed to do. Held as four uploads, attempt five gets commissioned in eighteen months by somebody who has forgotten the first three.
The contributor who now disagrees with herself. The foundry owner is on camera in the video that landed and in the one currently being edited, and she gives a different year for the closure decision in each. Both are honest and one is wrong. Because both appearances hang off one node, that is a thing you find in the edit. Because they were filmed fourteen months apart, it is a thing nobody finds otherwise.
The permission that expired in April. A fully scripted film is waiting on a location whose landowner permission lapsed four months ago. It expired quietly, the way permissions do. In the structure it is a video pointing at a permission marked expired, sitting one line apart, which is the difference between noticing now and noticing on the morning of the shoot.
The footage that paid for itself twice. Twenty-two minutes shot on a clear morning for a bridge film, of which ninety seconds were used. Another forty seconds went into the concrete video two years later, and it was findable because it was a thing with a name and not a folder named after the month it was shot in.
There are no tasks, no assignees, no sprints and no notifications. It does not want your footage, it will not cut or upload anything, and it has no opinion about your posting schedule. There is structured data underneath, because that is what makes the connections work, and it is one keypress to hide the panels where it lives.
Nothing is imported and nothing is migrated. Your notes are plain text files in a folder you chose on your own machine, which means stopping tomorrow costs you nothing and loses you nothing. There is no account, no sign-in and no telemetry, so nothing about an unreleased video goes anywhere at all. That last point is not a small one when half of what is in here is embargoed, unannounced or under an agreement.
An editor cutting an episode who needs to know what has already been said on camera by the person on screen. A researcher joining for a series. A brand that wants to see where their deliverable actually sits before they sign. A production partner who needs the access constraints on four locations without a phone call about each one.
Every one of them is asking for a version of the same document, and it is the one nobody writes, because writing it is a week of work that produces nothing new. A space can be sent as a link or a single file that opens in an ordinary browser, navigable, with the permits and the release forms attached where they belong. They install nothing, sign up for nothing and pay nothing, which is the only version of this that works for a freelancer you are hiring for four days.
You do not begin with a blank screen. A Template is a starting vocabulary, the kinds of thing that exist in a job and the ways they relate, so the categories are already there and already coloured when you make a space.
Nothing stops you using more than one Template in a space, and most channels end up doing exactly that: the production vocabulary for what gets made, the strategy vocabulary for what it is about. The worked example above is the two of them together, with permissions and obligations added because that is what the work turned out to need.
Everything on this page except the sending is on the free plan, permanently, with no account, no card and no trial quietly running out. Attachments are not limited, which matters when the permits and the release forms are the point.
Spaces are unlimited and the bridges between them are free, so a channel becomes a few linked spaces rather than one enormous one: the back catalogue in the first, the people and the permissions in the second, the commercial obligations in the third, all joined and all navigable. Each holds twenty nodes, which is roughly a season.
The paid tier is $120 a year and buys exactly one thing: sending a space to somebody who does not have Filamental. That is the freelance editor, the researcher, the production partner and the brand. If none of those apply to you yet, you never need to pay.
No. There is structured data underneath, because that is what makes the connections work, and you can go your whole life without opening it. Panels you do not want are hidden with a single key, and the parts most people actually use are a name, some notes and a line drawn to something else. Nothing is required to be filled in, and nothing nags you for leaving it empty.
No. It does not want your footage, it will not cut, render or upload anything, and it is not a task list with dates on it. It sits beside the tools you make the work in and holds what the channel is made of: the topics, contributors, locations, permissions, sponsor obligations and footage that recur, and how they relate to each other.
Folders hold files and lose relationships. A spreadsheet holds rows and loses them too. Neither can tell you that the contributor in the film you are editing said something on camera that contradicts what they said eighteen months ago, or that the scripted video in your backlog depends on a location permission that expired in April. Those are relationships between things, and a structure holds them where a folder cannot.
It holds the obligation as a thing joined to the video that discharges it, so what you owe and where it lands are one hop apart rather than in two different inboxes. It is not a calendar and it will not remind you. What it does is stop the deliverable and the film it lives in being tracked in two places that can disagree.
No. Everything is Markdown files with a few lines of structured data at the top, sitting in an ordinary folder you chose, on your own machine. Stop using it tomorrow and every note you wrote is still readable in any text editor on any computer. There is no database, no export step and no account, so there is nothing to be locked out of.
Yes, and it is the one thing the paid tier buys. Publisher turns a space into a document you send as a link or a single HTML file, and it opens in an ordinary browser with the structure navigable inside it. Whoever receives it installs nothing, creates no account and pays nothing, which is what makes it usable for a freelance editor or a brand you are pitching.
One evening and the channel you already have is enough to find out whether this suits how you think. Free, no account, no card, and nothing that leaves your machine.