Building a File Cluster for Your Post-Production Studio

The Problem with Studio File Sharing Today

A typical mid-size post house has five to ten edit suites, a color room, a sound stage, a couple of graphics workstations, and a NAS holding the master media. Getting files between those rooms usually involves some combination of a shared volume over SMB, a Finder window pointed at a mounted drive, and an intern with a USB stick when the network gets slow.

Then the remote editors show up. Suddenly you need VPN tunnels, cloud sync, or FTP servers — each with its own auth system, speed limits, and failure modes. The in-house team uses one workflow, the remote team uses another, and the assistant editor spends half the day making sure files land where they're supposed to.

SANs solve the real-time collaborative editing problem well — multiple editors on the same timeline with bin locking and shared playback. But most of the file movement in a studio isn't that. It's getting 200GB from Suite A to the colorist, syncing with a remote editor, or delivering finals to a client. That's a different problem that needs a different tool.

What a File Cluster Looks Like

With Handrive's clustering, every machine in your studio — and outside it — becomes a node in one connected network. You sign in with the same email on each device, and they all see the same shares, contacts, and file structure automatically. No server to configure. No VPN. No per-seat licenses.

┌────────────┐  ┌────────────┐  ┌────────────┐
│  Suite A   │  │  Suite B   │  │  Color     │
│  (Avid)    │  │  (Resolve) │  │  (Resolve) │
└─────┬──────┘  └─────┬──────┘  └─────┬──────┘
      │               │               │
      └───────┬───────┴───────┬───────┘
              │               │
        ┌─────┴──────┐  ┌────┴────────┐
        │  NAS       │  │  Graphics   │
        │  (Headless)│  │  (After Fx) │
        └─────┬──────┘  └─────────────┘
              │
     ─────────┼──────────── Internet ──
              │
        ┌─────┴──────┐  ┌────────────┐
        │  Remote    │  │  Sound     │
        │  Editor    │  │  (Remote)  │
        └────────────┘  └────────────┘
              

Every node talks directly to every other node via P2P. The NAS running in headless mode acts as the always-on anchor so transfers can happen even when workstations are off for the night. Remote editors connect through the same mechanism — no separate workflow, no different tool.

Setting It Up

Step 1: Install Handrive on Every Workstation

Desktop app for edit suites and graphics stations. Each editor signs in with the same studio email (or their own email if you prefer per-person accounts). Signing in is all it takes — shares appear automatically.

Step 2: Set Up a Headless Node on Your NAS

Your NAS becomes the always-on backbone. Install the Handrive CLI and register it as a system service so it survives reboots:

# On the NAS or studio server
hand auth login otp studio@yourcompany.com
hand service install
hand service start

That's it. The NAS is now a permanent node in your cluster. Files shared by any workstation are accessible through the NAS even when the originating machine goes offline. See the service command docs for platform-specific details.

Step 3: Run Multiple Instances for Throughput

This is where clustering gets interesting for studios with 10Gb+ networking. A single Handrive instance is fast, but if you have a server with a lot of CPU and a fat pipe, you can run multiple instances on different ports to saturate the link:

# Multi-instance for high-throughput servers
hand serve --port 4263
hand serve --port 4264
hand serve --port 4265

All instances share state automatically. You're effectively parallelizing your transfer capacity without any load balancer or orchestration layer. For studios ingesting camera originals from multiple shoots simultaneously, this can be the difference between media being ready for the morning edit session and still copying at lunch.

For production setups, use systemd templates so each instance starts on boot:

# /etc/systemd/system/handrive@.service
[Unit]
Description=Handrive Instance %i
After=network-online.target

[Service]
Type=simple
User=handrive
ExecStart=/usr/local/bin/hand serve --port %i
Restart=always

[Install]
WantedBy=multi-user.target

sudo systemctl enable handrive@4263 handrive@4264 handrive@4265
sudo systemctl start handrive@4263 handrive@4264 handrive@4265

Real Workflows This Enables

DIT to Edit: Same Day Turnaround

DIT on set shares camera originals to the studio cluster. Because the NAS is always on, files start arriving immediately. By the time the editor sits down, the media is already on the NAS and accessible from any edit suite. No waiting for hard drives to ship. No upload to a cloud bucket. The DIT doesn't even need to know which suite the editor is in — the files are available everywhere.

Editorial to Color: No Manual Handoff

Editor finishes a cut and drops the timeline export and handles into a shared folder. The colorist's workstation, already part of the cluster, has access instantly. No email with a link, no walking a drive down the hall. The files are already there because both machines are nodes in the same cluster.

Remote Sound Mix

Sound designer works from home. Their laptop is part of the same cluster. They pull the mix stems, work on them, and share back the final stems. To everyone else in the studio, it looks the same as if the sound designer were sitting in the next room. P2P handles the connection through NAT traversal — no VPN required.

Client Review Deliverables

Need to send a client a batch of review cuts? Create a share, add the client's email, drop the files in. They get access on their machine directly — encrypted, peer-to-peer, no file size limits, no download links that expire in 7 days.

Why Not Just Use a SAN?

SANs are purpose-built for real-time multi-user editing on the same timeline. If you need multiple editors cutting the same Avid project simultaneously with bin locking and real-time playback from shared storage, a SAN is the right tool.

Most file movement in a post house is distribution, not shared access: getting 300GB of camera originals from DIT to the NAS, moving a color session from one room to another, sending a mix to a remote sound editor, delivering finals to a client. SANs weren't designed for that workflow — they're optimized for the shared timeline use case.

A Handrive cluster handles the file distribution layer — the bulk of transfers that are “move this batch of files from A to B.” If you also have a SAN for real-time collaborative editing, they complement each other naturally. Different tools for different parts of the workflow.

What It Costs

Nothing. Handrive is free. No per-seat licensing, no per-GB pricing, no storage tier upsells. You're using your own hardware and your own network. The only cost is the hardware you already own.

Compare that to cloud transfer services that charge per-GB for every transfer, or shared storage solutions with annual maintenance contracts. For a studio moving terabytes weekly, the savings are significant.

Getting Started

The fastest way to test this: install Handrive on two machines in your studio, sign in with the same email on both, and share a folder. You'll see it appear on the other machine instantly. From there, add your NAS as a headless node and you have an always-on cluster running in minutes.