From Emergency Rescue to Infrastructure Backbone: QQ studio Storage Upgrade

About QQ studio QQ studio is a Czech production and postproduction company engaged in filmmaking and European television projects. For their visual effects (VFX) artists, editors, and sound designers, high data throughput and system reliability are critical. Data bottlenecks and hardware crashes risk missed client deadlines, broken delivery promises, and interrupted creative flow. The Breaking Point In mid-2024, QQ studio’s production pipeline hit a wall. Over 40 TB of active project data lived on an aging QNAP NAS. External access via FTP failed, forcing reliance on expensive third-party file transfer services like Frame.io. Meanwhile, project management relied on Kitsu, the studio’s central tool for tracking VFX shot status, coordinating task assignments, and reviewing preview renders across creators. For most modern companies, the automatic answer to a failing local server is simply: Move everything to the cloud. However, given QQ studio’s hybrid setup where editors, VFX artists, and render nodes work directly on local workstations, relying on remote storage isn’t practical. The studio works with massive, uncompressed video files where even a 2.5Gbps local network can sometimes feel slow. Pulling terabytes of raw footage down from the internet daily would cripple their creative workflow, and paying for 40+ TB of active, high-speed cloud storage would burn through project budgets entirely. They needed the massive speed of a local network, but with enterprise-grade reliability. Meanwhile, daily backups were manual and fragile, relying entirely on hope that systems wouldn't crash. With growing project scopes, a team scaling over 40 creators, and strict commitments to major partners, studio leadership knew their old infrastructure had reached its limits. They brought me in to work alongside their team and replace the fragile setup with a stable, secure foundation. Deploying the Industry Standard Rather than forcing a proprietary, unproven setup from scratch, I worked