The intake folder checks its own uploads

A video editor takes raw footage from clients. 40GB per shoot. The usual path is a WeTransfer link, a download to the laptop, a second upload to wherever the edit actually runs.

Now each client gets a files URL behind a password group. They drag the footage into the browser; it writes straight to the container's disk. No laptop in the middle.

The client's producer is nervous about corruption on a 40GB transfer. The editor sends one more URL: clip-0412.mov?hash. The service returns the SHA256 of what's on disk. The producer compares it against what they sent. Match. Done.

No transfer service, no expiring link, no second hop. The files land where the work happens, and they prove they arrived whole.

The files land where the work happens, and they prove they arrived whole.