Fogjaw

Super Drive replaced that split arrangement with one desktop app that could manage the files directly.

Syncing a file is not difficult in isolation. It gets difficult when a studio is working on the same project, files are large, people are spread around the world, connections disappear, somebody needs an older version, or two people try to change the same thing.

Those problems shaped what became Vault.

A studio’s main storage might be in the same office or a continent away. If another Fogjaw user closer to you already has the data, Fogjaw can fetch the available parts from that machine instead of hauling every copy back from the studio’s main storage. Interrupted transfers can continue where they stopped. People can work with only the parts of a project they need. Files can be locked when the work requires it, and previous versions remain recoverable.

The aim was never to build clever file-transfer software. It was to make the difficult parts disappear for the artist.

Once the file client worked, another thing started bothering me. An artist should not have to open Fogjaw just to find out whether a file is current, locked, syncing, or in conflict.

So that information moved to where the files already were. On Mac, Windows, and Linux, Fogjaw can show file state and actions beside the files themselves.

The same idea shaped integration work for tools such as Maya, Blender, and Unreal. If Fogjaw knows something useful about the work, it should show up where the artist is working rather than dragging them somewhere else to find it.

Once files were moving properly, the artificial boundary became obvious.

A file gets created. Someone else needs to see it. They make notes. Another version appears. It gets approved. It becomes an asset worth finding later. Eventually something gets delivered to a client. Meanwhile somebody has to know where the time went.

Small studios often handle those steps in different products, even though they are all describing the same work. Fogjaw grew around that path.

Review became part of the system because feedback belongs with the thing being reviewed. Asset management followed because versions eventually become things worth organising and finding. Delivery followed because approved work eventually has to leave the studio. Time tracking could use the work people were already doing instead of asking them to reconstruct their day afterwards.

What began as a replacement file client became a suite because the file was never really the whole problem.

A lot of Fogjaw came from noticing small bits of friction that software had taught people to accept.

Large transfers should not have to restart because a connection dropped.

A studio should not have to move the same large data across a continent when a closer machine already has it.

An artist should not have to ask whether somebody else is editing a file.

A reviewer should not have to describe which frame of a video they mean.

An external client should be able to securely receive, review, and approve work without becoming a member of the studio’s internal system.

Someone should not have to remember at five o’clock which project occupied their morning if the system already saw the work happening.

None of those is a grand technological problem by itself. Together they determine whether the software feels like infrastructure people have to manage, or something that quietly gets out of their way.