Vendor Jailing & Sparse Checkout¶

When collaborating with external freelancers (Vendors), studios face two critical bottlenecks: Intellectual Property (IP) Security and Bandwidth Waste. Forcing a remote animator to download a 500GB repository just to work on a single shot is highly inefficient and exposes your entire production data.

OpenStudioHub introduces a Zero-Trust architecture through its Vendor Jailing engine.

How It Solves the Problem¶

Instead of performing a full repository clone, the Hub evaluates the user's role upon login. If the artist is tagged as a vendor, the system automatically shifts to a highly restrictive Sparse Checkout mode.

1. Granular Downloads via Manifests¶

The system downloads only the specific task folder assigned to the artist. To ensure the 3D scene doesn't break, the Hub scans a local dependency manifest (*-meta.json) generated by the DCC. It then executes a recursive algorithm to fetch exclusively the exact textures, caches, and linked assets required for that specific shot.

2. Relative Path Translation¶

To avoid broken links without downloading massive parent folders, the Hub translates native Blender relative paths (//) into absolute Version Control System (VCS) paths. This guarantees zero broken links for the artist without saturating the production database.

3. Automated Workspace Purging¶

As a vendor finishes a task and moves to a new one, the Hub automatically purges the old, approved shots from their local hard drive. This prevents progressive IP leakage and keeps the freelancer's workstation lightweight and focused.